Quote:
|
Originally Posted by Ignition
Sorry I don't think the slow responses are due to ntl, and the fact that other customers on that provider using the 'nicer' transits seeing slower responses indicates this.
The ping differences could just be different routes being taken along the fibre rings across the atlantic in the case of Tiscali.
That said there is some routing weirdness on ntl's network which I've documented elsewhere as yet to no response.
It does give the impression that ntl's 'MPLS' network is being configured manually 
BTW Chrysalis why are you complaining about 125ms from Texas and ~80 from New York? I mean wtf dude? |
I am not latency is ok, but with lag spikes. It is the speed I have a problem with mainly.
I am very curious whats going on with the transit routing at the moment as to why it is been routed differently to most of the other ntl network nodes.
---------- Post added at 15:34 ---------- Previous post was at 15:30 ----------
here is my outbound route and is over 150ms due to some obscene routing to manchester then london.
many spikes as well due to ubr problems.
Tracing route to web1.imagis.info [72.232.25.42]
over a maximum of 30 hops:
1 7 ms 13 ms 10 ms UBR [10.8.143.254]
2 24 ms 28 ms 12 ms leic-t2cam1-a-ge914.inet.ntl.com [82.3.35.149]
3 29 ms 19 ms 19 ms leic-t2core-a-ge-210-0.inet.ntl.com [82.3.33.6]
4 21 ms 20 ms 17 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110]
5 13 ms 18 ms 25 ms lee-bb-b-ae0-0.inet.ntl.com [62.253.187.186]
6 25 ms 23 ms 55 ms man-bb-a-so-700-0.inet.ntl.com [62.253.185.193]
7 24 ms 25 ms 65 ms 212.187.137.1
8 29 ms 43 ms 23 ms so-6-0-0.mp2.manchesteruk1.level3.net [4.68.113.
114]
9 48 ms 25 ms 36 ms ae-1-0.bbr2.london1.level3.net [212.187.128.57]
10 25 ms 26 ms 27 ms ge-6-0.core2.london1.level3.net [4.68.116.36]
11 41 ms * 29 ms bcr1-so-4-0-0.londonlnx.savvis.net [206.24.169.2
9]
12 41 ms 46 ms 49 ms bcs1-so-1-1-0.londonlnx.savvis.net [204.70.193.1
14]
13 151 ms 104 ms 138 ms bcs2-so-0-0-0.newyork.savvis.net [204.70.192.121
]
14 178 ms 123 ms 112 ms bcs2-so-4-0-0.washington.savvis.net [204.70.192.1]
15 132 ms 112 ms 120 ms dcr2-so-7-2-0.Atlanta.savvis.net [204.70.192.57]
16 136 ms 155 ms 143 ms bcs2-so-2-0-0.dallas.savvis.net [204.70.192.70]
17 133 ms 147 ms 181 ms bcs1-so-6-0-0.dallas.savvis.net [204.70.192.49]
18 199 ms 155 ms 190 ms ohr1-pos-4-0.fortworthda1.savvis.net [208.172.131.82]
19 145 ms 156 ms 145 ms csr1-ve240.fortworthda1.savvis.net [216.39.64.34]
20 132 ms 152 ms 146 ms 216.39.79.214
21 * * * Request timed out.
22 157 ms 191 ms 151 ms 42.25.232.72.reverse.layeredtech.com [72.232.25.42]
Abyss I havent seen a trace from you, you blaming LT but I see nothing from you indicating that.