So I switched my servers from a VPS to a dedicated due to some on sale.

[quake-legion.net]

Round trip time to 64.120.26.130: 46 ms
Round trip time to 64.120.26.130: 47 ms
Round trip time to 64.120.26.130: 40 ms
Round trip time to 64.120.26.130: 40 ms
Round trip time to 64.120.26.130: 40 ms
Round trip time to 64.120.26.130: 40 ms
Round trip time to 64.120.26.130: 40 ms
Round trip time to 64.120.26.130: 40 ms
Round trip time to 64.120.26.130: 42 ms
Round trip time to 64.120.26.130: 43 ms

Average time over 10 pings: 41.8 ms

I ping 60ms average inside quake, hmm can anyone tell me what's going on :-].

I think this happened before when I first had the server on a VPS, and within a few hours my ping went back to normal in quake.

So does anyone here know much about networking? I know the basics and that's it.

Not a networking pro but common sense tells me there is game overhead associated with QW and the ping will always be a bit higher than what OS utilities report.

IIRC, the original QW client had a minimum ping of 56 (or so) and I never saw a fix until I think ZQuake had a hack to up the priority of the process in the OS that lowered the ping. Remember now, I've lost lots of brain cells in the time that has passed so I could remember it incorrectly.

your quakeworld client will add a ping of 1000/$framerate.
(this generally comes out as 13 to 14 extra ms).
Not sure where the extra 4-5ms comes from. Your ping isn't totally stable, so I assume wireless, in which case quakeworld's datarates are probably triggering a little packetloss, which your wireless router might be resending automatically without quake ever knowing. Perhaps.
I have no idea. I don't even work here.

The most basic way to approach such problems is to use traceroute and find out on which device the latency is gained. hth

Minimum ping 54 would happen in qwsv if you ran it on a Windows 9x machine due to poor choice of time function. And the priority boost was necessary if you wanted to run a dedicated server on the machine you were playing.