network delay

Take a look at these traceroutes to suspicious:

river:~ tboyes$ traceroute dns.suspicious.org
traceroute to dns.suspicious.org (216.254.67.211), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 3.615 ms 5.729 ms 7.828 ms
2 222-155-0-1.jetstream.xtra.co.nz (222.155.0.1) 62.499 ms 70.749 ms 65.100 ms
3 * * *
4 * 202.50.232.205 (202.50.232.205) 254.055 ms 263.302 ms
5 so0-2-3.tkbr9.global-gateway.net.nz (202.50.232.34) 261.803 ms 235.589 ms 202.724 ms
6 so1-1-3.labr5.global-gateway.net.nz (202.50.232.18) 327.337 ms so-1-1-2.labr5.global-gateway.net.nz (202.50.232.234) 344.120 ms so1-1-3.labr5.global-gateway.net.nz (202.50.232.18) 411.842 ms
7 * * *
8 * sl-st20-la-6-2.sprintlink.net (144.232.154.209) 239.053 ms 239.333 ms
9 * * 144.232.9.18 (144.232.9.18) 259.744 ms
10 los-core-01.inet.qwest.net (205.171.32.9) 1562.551 ms 259.579 ms *
11 * * *
12 * jfx-edge-01.inet.qwest.net (205.171.230.110) 3137.821 ms 324.274 ms
13 * * *
14 * * 220.ge-3-0.er1.nyc1.speakeasy.net (69.17.83.202) 3828.562 ms
15 dns.suspicious.org (216.254.67.211) 2006.157 ms * 2136.278 ms

---

Originally published on truman.net. See the archived copy.