Traceroute

Reading the hops

Each line is a router on the path, with the time it took to answer. The network name (ASN) shows which provider each hop belongs to, so you can see where traffic leaves one network and enters the next.

• A jump in latency that continues on every following hop shows where delay is added — often a long-distance link, which is normal.
• A slow hop followed by fast ones is usually just a router that answers traceroute slowly; it isn’t the problem.
• * means a router didn’t reply. Many are configured that way. It only matters if every hop after it is also silent and the destination is never reached.

Why it differs from your own traceroute

This trace runs on Globalping’s probe network from a location somewhere in the world, so it follows a different path than one started from your office. Internet routes are also often asymmetric: the way back can differ from the way there. For a problem on your own connection, run tracert (Windows) or traceroute / mtr (macOS, Linux) locally and compare.