![]() |
News | Profile | Code | Photography | Looking Glass | Projects | System Statistics | Uncategorized |
Blog |
Telia / NAC have really been annoying me, lately:
traceroute to hsa1.NewYork1.Level3.net (209.244.2.210), 64 hops max, 60 byte packets
1 voxel.prolixium.net (69.9.189.181) 0.634 ms
2 499.ge-6-1-0.gbr2.oct.nac.net (216.118.70.178) 0.809 ms
3 0.ge-0-0-0.gbr1.oct.nac.net (209.123.11.49) 1.036 ms
4 0.so-2-2-0.gbr1.tl9.nac.net (209.123.11.143) 89.376 ms
5 nyk-b1-link.telia.net (80.91.250.161) 13.986 ms
6 te-4-2.car2.NewYork1.Level3.net (4.68.110.81) 13.138 ms
7 lo-0.hsa1.NewYork1.Level3.net (209.244.2.210) 15.210 ms
Normally, I wouldn't care, but look at the trend. Average (well, used to be) RTT to anything in Manhattan is roughtly 3 ms. NAC is one of Voxel's transit providers, and Telia is one of NAC's. Ironically, Voxel had network capacity upgrades on the 19th and 20th. They also have Level(3) as transit, but I suppose are now taking advantage of hot potato routing (BGP) in order to whisk packets from inexpensive servers (mine) out cheaper transit (NAC).
Oh, yeah, this is killing my IPv6 latency :P
New comments are currently disabled for this entry.
![]() ![]() ![]() ![]() ![]() |
This HTML for this page was generated in 0.000 seconds. |