I ran traceroute for the first time in a while, and I'm a little curious about the results:
Code:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 5 ms 10.33.34.37
3 4 ms 5 ms 4 ms P9-1.LCR-04.DLLSTX.verizon-gni.net [130.81.58.134]
4 4 ms 4 ms 5 ms so-7-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.81.17.175]
5 6 ms 7 ms 7 ms POS2-0.GW10.DFW9.ALTER.NET [152.63.97.57]
6 6 ms 7 ms 7 ms 0.so-3-1-0.XT2.DFW9.ALTER.NET [152.63.101.134]
7 8 ms 7 ms 7 ms 0.so-7-0-0.XL4.DFW13.ALTER.NET [152.63.98.81]
8 7 ms 7 ms 7 ms POS7-0.GW1.DFW13.ALTER.NET [152.63.103.89]
9 45 ms 47 ms 50 ms theplanet-gw.customer.alter.net [157.130.143.226]
10 44 ms 44 ms 44 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]
11 45 ms 44 ms 45 ms vl22.dsr02.dllstx2.theplanet.com [70.85.127.76]
12 44 ms 44 ms 45 ms vl1.car02.dllstx2.theplanet.com [12.96.160.12]
(last hop omitted)
Note the big jump in latency from hop 8 to hop 9. In the past, there hasn't been a significant increase at this point, and I was seeing about 9 ms latency end-to-end. At one time, I waited for a while until a Linode was available in Dallas, because I wanted the low latency.
In all honesty, I don't think it makes a big difference. But, I'm wondering if it's an indication of a problem that is brewing. If so, who should I notify?
FAQ
Search
Members
Register
Login [ Anonymous ]
