View Single Post
Join Date: Jun 2012
Posts: 441
# 11
11-24-2012, 10:29 PM
Originally Posted by xlocutusofborgx View Post

this is all pretty gibberish to me lol.
How a traceroute works is each hop is sent three packets of data per hop--those numbers in ms on each hop is the time it takes for each packet to reach the specified point on the far right (either a website or a relay server).

Looks like there's some high, but not completely problematic lag in the last few hops on your trace (those servers appear to me from their names to be in the Boston area, which may still be dealing with the aftermath of Sandy--internet infrastructure is usually low on the priority list, and being a major storm survivor myself, I know those sort of things can take months and months to get just right again)

The last two hops (including the one ending at the patch server itself, the address at the end of your trace) is awfully high as well.
Lagging, D/Cing, or rubberbanding? Here's some help.

Current ships: A lot. RTR 15 National Championships....and counting

Last edited by lewstelamon01; 11-24-2012 at 10:33 PM.