Quote:
|
Originally Posted by StuS
3 9 ms 9 ms 9 ms lutn-t2cam1-a-v135.inet.ntl.com [62.252.67.101]
4 11 ms 9 ms 9 ms lutn-t2core-a-ge-wan61.inet.ntl.com [213.107.47.65]
5 10 ms 9 ms 9 ms pop-bb-a-so-201-0.inet.ntl.com [62.253.188.185]
6 13 ms 11 ms 12 ms nth-bb-b-so-400-0.inet.ntl.com [213.105.172.13]
7 16 ms 15 ms 16 ms lee-bb-a-so-600-0.inet.ntl.com [62.253.185.102]
8 19 ms 20 ms 19 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
9 29 ms 29 ms 29 ms amst-ic-1-as0-0.inet.ntl.com [62.253.188.94]
10 75 ms 75 ms 75 ms ams-ix-nkf-1.router.nl.demon.net [195.69.144.99]
11 75 ms 160 ms 77 ms tc1-core-2-ge-1-0-1-0.router.nl.demon.net[82.161.255.5]
12 75 ms 76 ms 80 ms sin-core-1-at-1-2-1-0.router.nl.demon.net [82.161.255.26]
13 104 ms 106 ms 103 ms games.router.nl.demon.net [195.11.247.144]
something's broken  |
Two things, the UK route is odd, Luton, Poplar-A, Northampton, Leeds, Poplar-B, second obviously there's an issue on AmsIX between ntl and Demon.
No idea whose port is congested though, that'll have to be tested by someone on ntl who has something else in AmsIX to ping, perhaps news-europe.giganews.com will have the answers?
http://www.giganews.com/performance.html reports my reverse traceroute from there as being 13 - 15ms.
These guys have 10Gbit ports at AmsIX so should be an EXCELLENT test of ntl's peering, theirs is somewhat unlikely to be in strife
