Routing problem to oversee's sites

badnbusy · 11-10-2004, 20:24

Im having a rather annoying problem to sites abroad.

When I traceroute them, the problem appears to be outside the ntl network each time, but ive got a hunch that the problem is still related to ntl somehow.

I have a server in the US, and here are the results to it:

Quote:

Tracing route to ivhou-207-218-245-110.ev1.net
over a maximum of 30 hops:

1 5 ms 7 ms 7 ms 1.1.1.1
2 11 ms 11 ms 11 ms 10.22.48.1
3 11 ms 11 ms 11 ms oldh-t2cam1-b-ge92.inet.ntl.com [80.5.164.129]
4 12 ms 11 ms 11 ms mant-t2core-b-ge-wan82.inet.ntl.com [213.104.242.205]
5 19 ms 11 ms 11 ms man-bb-b-so-130-0.inet.ntl.com [213.105.174.22]
6 19 ms 19 ms 22 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
7 19 ms 19 ms 23 ms bre-bb-b-so-100-0.inet.ntl.com [213.105.172.234]
8 20 ms 20 ms 19 ms telc-ic-1-so-100-0.inet.ntl.com [62.253.188.117]
9 19 ms 23 ms 19 ms 195.66.226.185
10 97 ms 97 ms 97 ms p6-0.core02.jfk01.atlas.cogentco.com [154.54.1.5]
11 97 ms 97 ms 101 ms p12-0.core02.jfk02.atlas.cogentco.com [66.28.4.169]
12 97 ms 97 ms 108 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.13]
13 98 ms 97 ms 97 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81]
14 113 ms 120 ms 120 ms p14-0.core01.atl01.atlas.cogentco.com [66.28.4.161]
15 117 ms 120 ms 132 ms p14-0.core01.mco01.atlas.cogentco.com [66.28.4.153]
16 121 ms 124 ms 120 ms p14-0.core01.tpa01.atlas.cogentco.com [66.28.4.142]
17 137 ms 136 ms 136 ms p5-0.core01.iah01.atlas.cogentco.com [66.28.4.45]
18 375 ms 358 ms 378 ms everyonesinternet.demarc.cogentco.com [38.112.12.186]
19 375 ms 386 ms 374 ms ivhou-207-218-245-110.ev1.net [207.218.245.110]

Now a trace FROM my server TO my ntl ip shows:

Quote:

traceroute to 213.106.xxx.xxx (213.106.xxx.xxx), 30 hops max, 38 byte packets
1 ev1s-66-98-186-1.ev1servers.net (66.98.186.1) 0.481 ms 0.497 ms 0.598 ms
2 ivhou-207-218-245-7.ev1.net (207.218.245.7) 0.539 ms 0.470 ms 0.356 ms
3 ivhou-207-218-223-2.ev1.net (207.218.223.2) 0.488 ms 0.475 ms 0.444 ms
4 289.ge-4-2-1.mpr1.iah1.us.above.net (216.200.251.50) 1.188 ms 1.228 ms 1.168 ms
5 so-0-0-0.mpr2.iah1.us.above.net (64.125.31.62) 1.324 ms 1.349 ms 1.375 ms
6 pos0-0.mpr1.atl4.us.above.net (64.125.29.69) 137.105 ms 97.114 ms 97.135 ms
7 pos15-0.mpr2.atl4.us.above.net (64.125.29.246) 97.011 ms 97.062 ms 97.296 ms
8 so-5-3-0.cr1.dca2.us.above.net (64.125.28.49) 25.421 ms 25.218 ms 25.333 ms
9 so-6-0-0.cr1.lhr3.uk.above.net (64.125.31.185) 115.209 ms 123.868 ms 123.455 ms
10 pop-bb-b-so-330-0.inet.ntl.com (208.185.188.42) 363.645 ms 366.214 ms 360.864 ms
11 lee-bb-a-so-700-0.inet.ntl.com (62.253.185.237) 368.459 ms 352.198 ms 374.502 ms
12 lee-bb-b-ae0-0.inet.ntl.com (62.253.187.186) 370.715 ms 387.585 ms 370.996 ms
13 man-bb-a-so-700-0.inet.ntl.com (62.253.185.193) 365.578 ms 364.268 ms 350.325 ms
14 mant-t2core-a-pos71.inet.ntl.com (213.105.174.17) 370.793 ms 363.420 ms 350.054 ms
15 oldh-t2cam1-a-ge-wan31.inet.ntl.com (213.104.242.42) 358.674 ms 369.641 ms 357.735 ms
16 ubr01oldh-ge10.inet.ntl.com (80.5.164.2) 361.490 ms 349.771 ms 348.931 ms

As you can see, the problem comes into play at hop 10, as it enters ntl's network (pop-bb-b-so-330-0.inet.ntl.com (208.185.188.42))

Also a trace to google.com:

Quote:

Tracing route to google.com [216.239.57.99]
over a maximum of 30 hops:

1 2 ms 7 ms 7 ms 1.1.1.1
2 11 ms 11 ms 11 ms 10.22.48.1
3 12 ms 10 ms 11 ms oldh-t2cam1-a-ge92.inet.ntl.com [80.5.164.1]
4 55 ms 19 ms 11 ms mant-t2core-a-ge-wan64.inet.ntl.com [213.104.242.53]
5 12 ms 11 ms 11 ms man-bb-a-so-210-0.inet.ntl.com [213.105.174.18]
6 19 ms 23 ms 19 ms 212.187.137.1
7 19 ms 19 ms 25 ms so-10-0.hsa1-new.manchesteruk1.level3.net [4.68.113.97]
8 19 ms 19 ms 19 ms ae1-0.bbr2.London1.Level3.net [212.187.128.57]
9 101 ms 85 ms 85 ms as-0-0.bbr1.newyork1.level3.net [4.68.128.106]
10 162 ms 159 ms 158 ms ge-0-1-0.bbr2.sanjose1.level3.net [64.159.1.130]
11 164 ms 160 ms 163 ms ge-9-2.ipcolo2.sanjose1.level3.net [64.159.2.164]
12 383 ms 378 ms * unknown.level3.net [209.247.202.218]
13 385 ms 382 ms 386 ms 216.239.47.194
14 383 ms 392 ms 386 ms 216.239.49.2
15 391 ms 386 ms 381 ms 216.239.57.99

and also a trace to the Virgin radio mp3 stream:

Quote:

Tracing route to shoutcast.llnw.net [69.28.128.148]
over a maximum of 30 hops:

1 6 ms 7 ms 7 ms 1.1.1.1
2 11 ms 11 ms 11 ms 10.22.48.1
3 12 ms 15 ms 11 ms oldh-t2cam1-a-ge92.inet.ntl.com [80.5.164.1]
4 12 ms 11 ms 15 ms mant-t2core-a-ge-wan64.inet.ntl.com [213.104.242.53]
5 12 ms 11 ms 12 ms man-bb-a-so-210-0.inet.ntl.com [213.105.174.18]
6 11 ms 11 ms 11 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]
7 12 ms 11 ms 22 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
8 19 ms 19 ms 18 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
9 19 ms 19 ms 26 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
10 19 ms 19 ms 18 ms cr02.ldn01.pccwbtn.net [195.66.224.167]
11 324 ms 308 ms 323 ms ge0-3-0-8.jr1.iad.llnw.net [63.218.94.10]
12 382 ms * 418 ms so5-0-3.jr1.lax.llnw.net [69.28.172.18]
13 410 ms 421 ms 409 ms so7-0-0.jr1.phx1.llnw.net [69.28.172.42]
14 422 ms * 410 ms ge1-1-0.jr1.phx3.llnw.net [69.28.139.250]
15 421 ms 419 ms 400 ms shoutcast.llnw.net [69.28.128.148]

and to cap it off, microsoft.com:

Quote:

Tracing route to www.microsoft.com.nsatc.net [207.46.156.188]
over a maximum of 30 hops:

1 3 ms 7 ms 7 ms 1.1.1.1
2 12 ms 11 ms 14 ms 10.22.48.1
3 11 ms 11 ms 11 ms oldh-t2cam1-a-ge92.inet.ntl.com [80.5.164.1]
4 15 ms 26 ms 11 ms mant-t2core-a-ge-wan81.inet.ntl.com [213.104.242.73]
5 12 ms 11 ms 11 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
6 19 ms 19 ms 19 ms 212.187.137.1
7 19 ms 18 ms 19 ms so-10-0.hsa1-new.manchesteruk1.level3.net [4.68.113.97]
8 19 ms 19 ms 19 ms ae-1-0.bbr1.London2.Level3.net [212.187.128.46]
9 90 ms 89 ms 93 ms as-0-0.bbr2.washington1.level3.net [4.68.128.102]
10 152 ms 155 ms 152 ms so-1-0-0.mp2.seattle1.level3.net [209.247.10.133]
11 156 ms 155 ms 155 ms ge-10-2.hsa1.seattle1.level3.net [209.247.9.74]
12 167 ms 171 ms 167 ms unknown.level3.net [63.211.220.82]
13 168 ms 171 ms 171 ms gig6-0.core2.sea1.ntwk.msn.net [207.46.40.129]
14 406 ms 398 ms 401 ms pos1-0.iusnixcpxc1201.ntwk.msn.net [207.46.36.210]
15 410 ms 417 ms 409 ms pos1-0.iuscixwstc1201.ntwk.msn.net [207.46.155.17]
16 * * * Request timed out.

So, yeah, although the ping hikes come after the ntl network, could this still be down to an issue on their side? I cant believe that the above 4 sites all have problems. It just seems too coincidental.

Maybe there is an overall 'peering to the US' problem?

Any help would be appreciated.

James

badnbusy · 11-10-2004, 21:00

Update: Cant even reach Paypal.com whatsoever :S

Stop It · 11-10-2004, 22:01

The problem starts in between the US and UK, rather than at ntl, looks like a congested US-UK backbone, probably,

IanUK · 11-10-2004, 22:24

I'm getting almost identical traces and terrible throughput here as well.
Looks like something has gone wrong somewhere

Ian

IanUK · 11-10-2004, 23:15

2 of my traces:

Tracing route to geocities.com [66.218.77.68]

over a maximum of 30 hops:

1 6 ms 7 ms 5 ms 10.82.176.1

2 7 ms 7 ms 7 ms wapk-t2cam1-b-ge-wan41-112.inet.ntl.com [80.1.1

0.185]

3 7 ms 6 ms 7 ms popl-t2core-b-ge-wan61.inet.ntl.com [62.255.81.

41]

4 7 ms 7 ms 6 ms pop-bb-b-so-320-0.inet.ntl.com [62.253.185.69]

5 226 ms 229 ms 230 ms so-3-0-0.cr1.lhr3.uk.above.net [208.185.188.41]

6 298 ms 299 ms 301 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]

7 300 ms 300 ms 301 ms so-0-0-0.cr2.dca2.us.above.net [64.125.29.122]

8 327 ms 330 ms 327 ms so-2-3-0.cr2.dfw2.us.above.net [64.125.29.13]

9 326 ms 325 ms 329 ms so-0-0-0.cr1.dfw2.us.above.net [64.125.28.209]

10 380 ms 372 ms 373 ms so-3-1-0.mpr4.sjc2.us.above.net [64.125.29.49]

11 374 ms 372 ms 372 ms pos6-0.mpr2.pao1.us.above.net [64.125.29.162]

12 372 ms 371 ms 372 ms pos2-0.mpr1.pao1.us.above.net [64.125.29.181]

13 373 ms 372 ms 370 ms yahoo-above-1.pao1.above.net [64.125.31.230]

14 157 ms 157 ms 159 ms vl10.bas1.scd.yahoo.com [66.218.64.134]

15 158 ms 158 ms 152 ms unknown-66-218-82-238.yahoo.com [66.218.82.238]

16 158 ms 372 ms 158 ms intl1.geo.vip.scd.yahoo.com [66.218.77.68]

Trace complete.

and

Tracing route to www.steampowered.com [69.28.175.115]

over a maximum of 30 hops:

1 6 ms 5 ms 6 ms 10.82.176.1

2 8 ms 6 ms 6 ms wapk-t2cam1-b-ge-wan41-112.inet.ntl.com [80.1.17

0.185]

3 8 ms 7 ms 7 ms popl-t2core-b-ge-wan62.inet.ntl.com [62.255.81.1

73]

4 7 ms 8 ms 7 ms pop-bb-b-so-320-0.inet.ntl.com [62.253.185.69]

5 8 ms 8 ms 9 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]

6 9 ms 8 ms 8 ms cr02.ldn01.pccwbtn.net [195.66.224.167]

7 303 ms 302 ms 298 ms ge0-3-0-8.jr1.iad.llnw.net [63.218.94.10]

8 375 ms 378 ms 375 ms so5-0-3.jr1.lax.llnw.net [69.28.172.18]

9 386 ms 382 ms 388 ms so7-5-0.jr1.phx1.llnw.net [69.28.172.62]

10 388 ms 390 ms 385 ms ge1-0-0-5.jr1.phx3.llnw.net [69.28.139.254]

11 388 ms 388 ms 384 ms www.steampowered.com [69.28.175.115]

Trace complete.

Mick Fisher · 12-10-2004, 00:23

Traceroute from Easynews.com

HOST LOSS RCVD SENT BEST AVG WORST
ge2-8-1000m.sw1.easynews.com0%

10100.440.610.93ae0-4000m-core-02.phx1.puregig.net0%

10100.458.7481.72ge0-0-0-51.jr1.phx1.llnw.net0%

10109.0112.3026.23so7-0-0.jr1.lax.llnw.net0%

101011.1813.3422.37so7-3-0.jr1.sjc.llnw.net0%

101020.1521.3027.28ge-4-1-0.mpr1.sjc7.us.mfnx.net0%

101018.6224.5757.7364.125.30.1780%

101019.0421.6235.55so-3-3-0.cr1.dfw2.us.above.net0%

101075.4276.5283.88so-0-0-0.cr2.dfw2.us.above.net0%

101075.4080.9597.73so-2-0-0.cr2.dca2.us.above.net0%

101074.8575.5878.7464.125.29.1210%

101074.8083.64112.61so-6-0-0.cr1.lhr3.uk.above.net0%

1010146.28149.67165.78pop-bb-b-so-330-0.inet.ntl.com10%

910371.41375.39378.85lee-bb-a-so-700-0.inet.ntl.com10%

910370.38373.86376.41nth-bb-b-so-000-0.inet.ntl.com10%

910373.91377.93382.00nrth-t2core-b-pos31.inet.ntl.com10%

910377.04378.83386.44nrth-cache-5.server.ntli.net10%

910373.33381.65408.82

The router most likely responsible for your slow downloads in owned by ntl.com.

I've been getting 25kB/s from a 192kB/s connection all day.
As for the cap/limit, call it what you will but IMO it is cynical in that, if you don't use it all on a day then it is lost. On the face of it 1gig a day looks to be on a par with 30gig a month but it is not. I note there are no refunds for only downloading 15gig a month cause your daily allowance don't roll over.

Since new TV menu came in I have to reboot my STB every day. Since the BB speed increases I have had intermittant problems of one type or another almost constantly.
Ntl's whole network seems to going to pot IMO.

Mick.