If that is the last hop before is hits the servers, then the issue will more than likely be an asynchronous route and the actual problem is on the return trip to your computer.
I'll have to run a trace from the server back to you tomorrow.
Think about it. If the hop just before our server was suffering really bad packet loss and/or wildly varying ping times, it would effect everyone in the same exact manner, without fail.
That is why I am pretty sure the problem is on the return trip, but I will not know where until tomorrow.