Network tools

Traceroute

Trace the network path from Network Crap's server to a public host, save runs, and compare how the path changes over time.

Traceroute is available to registered users with a verified email address. It runs real network probes from this server, so every run is tied to an account and rate-limited.

Sign in Create an account

Example: trace to 8.8.8.8 DEMO

A real traceroute this server ran, shown so you can see what a finished result looks like — including the toggles below.

No sustained latency jump was found on this path.

HopResponderProbesMedianNotes
1 172.31.86.2 18.53 ms   18.41 ms   18.32 ms 18.4 ms
2 172.31.86.254 1.30 ms   1.24 ms   1.17 ms 1.24 ms
3 75.160.223.37
72.31.136.29
4.51 ms   9.44 ms   4.37 ms 4.51 ms Several routers answered (load balancing).
4 71.46.8.141
130.13.160.1
10.38 ms   10.40 ms   4.15 ms 10.4 ms Several routers answered (load balancing).
5 No reply *   *   * — Router did not reply to probes; this is common and not necessarily a fault.
6 71.46.25.50 15.28 ms   15.79 ms   15.55 ms 15.5 ms
SLOW REPLY ONLY This router answered about 11 ms slower than the hop before, but later hops are faster. That is the router being slow to reply to probes, not a slow path.
7 72.14.215.76 7.72 ms   8.22 ms   6.26 ms 7.72 ms
8 192.178.96.229
192.178.109.83
192.178.109.89
18.60 ms   16.55 ms   21.39 ms 18.6 ms
SLOW REPLY ONLY This router answered about 10 ms slower than the hop before, but later hops are faster. That is the router being slow to reply to probes, not a slow path.
Several routers answered (load balancing).
9 209.85.242.133
8.8.8.8
108.170.232.201 DESTINATION
10.42 ms   9.47 ms   19.99 ms 10.4 ms Several routers answered (load balancing).