a ongoing problem that just escalated need ntl attention
 

ok for a good few weeks traceroutes have been bad, justanothernoob told me some upgrades were coming to leics which is good but just now this has happened, the problem has got completely out of hand and various parts of the net are down for me.

Tracing route to 62.132.1.50 over a maximum of 30 hops

1 7 ms 6 ms 7 ms 10.146.103.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * 13 ms so-7-0.hsa2.London1.Level3.net [212.113.14.129]

7 13 ms 13 ms 11 ms ae-0-12.gar2.London1.Level3.net [212.187.131.48]

8 11 ms 11 ms 16 ms so-6-0.metro1-londencyh00.London1.Level3.net [21
2.113.3.30]
9 15 ms 13 ms 11 ms ldn-s2-rou-1002.UK.eurorings.net [195.66.224.54]
10 14 ms 13 ms 11 ms ldn-s2-rou-1001.UK.eurorings.net [134.222.231.61
]
11 33 ms 30 ms 33 ms ffm-s1-rou-1002.DE.eurorings.net [134.222.230.12
1]
12 27 ms 27 ms 28 ms ffm-s1-rou-1077.DE.eurorings.net [134.222.104.37
]
13 28 ms 27 ms 32 ms 62.132.1.50

Tracing route to cableforum.co.uk [66.199.235.18]
over a maximum of 30 hops:

1 11 ms 7 ms 8 ms 10.146.103.254
2 7 ms 10 ms 8 ms leic-t2cam1-a-ge96.inet.ntl.com [80.7.30.17]
3 9 ms 7 ms 14 ms leic-t2core-a-ge-220-0.inet.ntl.com [82.3.33.10]

4 20 ms 13 ms 10 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110]

5 13 ms 15 ms 12 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

6 16 ms 15 ms 14 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]

7 17 ms 16 ms 14 ms linx.ge-0-0-0.gbr1.ltn.nac.net [195.66.224.94]
8 91 ms 84 ms 84 ms 0.ge-6-2-0.gbr2.nyc.nac.net [209.123.11.181]
9 82 ms 86 ms 83 ms 94.gi4-2.esd1.nyc.nac.net [64.21.102.14]
10 85 ms 83 ms 88 ms 10.gi1-1.esd1.tlw.nac.net [209.123.11.230]
11 87 ms 88 ms 88 ms ezzi.customer.tlw.nac.net [207.99.110.174]
12 87 ms 86 ms 87 ms 65.125.239.146

that however looks very good, my guess is traffic using london level 3 is broken (2 level3 outages in london this month is this a 3rd??)

Re: a ongoing problem that just escalated need ntl attention
 

hmm i spoke too soon :D

ntl rerouted traffic to abovenet all good now and the ms is low :D

Tracing route to 62.132.1.50 over a maximum of 30 hops

1 8 ms 6 ms 7 ms 10.146.103.254
2 7 ms 11 ms 7 ms leic-t2cam1-a-ge96.inet.ntl.com [80.7.30.17]
3 10 ms 11 ms 11 ms leic-t2core-a-ge-220-0.inet.ntl.com [82.3.33.10]

4 11 ms 11 ms 13 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110]

5 13 ms 14 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

6 14 ms 12 ms 17 ms so-3-0-0.cr1.lhr3.uk.above.net [208.185.188.41]

Re: a ongoing problem that just escalated need ntl attention
 

http://www.ntl-isp.ntl.com/ServiceStatus/

Says theres a fault with the Leicester area, so it has got ntl attention :P

Re: a ongoing problem that just escalated need ntl attention
 

yep I am posting update, pc was turned of at 3am after ALL sites died and all * * * in traceroute (still had ip), I turned it back on at 5pm and was stuck with a 169.x address, rang up fault reporting and after numerous options it had an answering machine saying Leicester outage and surrounding areas, I came back at 5.20pm and was able to get my ip address however a LOT of sites including google.co.uk dont work and traceroutes are a complete mess with numerous ntl hops timing out.

Leicester seems to have a rought time with ntl :(

Re: a ongoing problem that just escalated need ntl attention
 

things seem back to normal now and there is a new hop with a no-name dns but status still red on service page.

Re: a ongoing problem that just escalated need ntl attention
 

Leicester's had a massive upgrade this week - disruption unavoidable, but you now get your own routers instead of funnelling through Notts. Welcome to the big time.

Re: a ongoing problem that just escalated need ntl attention
 

yeah downtime for upgrade I got no problem with that :D

I need to give ntl a ring tho I still got the problem with godaddy ssl not working, very strange issue from a few weeks back that I can only use the site through my own proxy server and for obvious reasons I dont want to be proxying to ssl sites.

Re: a ongoing problem that just escalated need ntl attention
 

Ummm right, and we have maintenance windows during the middle of the night for what reason? Neither this type of upgrade nor any other upgrade should have the consequence of breaking people's internet access during the day, there's no positive spin there. This was a massive fault due to the upgrade.

Apologies for the grief caused to customers in Leicester, and hope you enjoy your shiny new connectivity.

Re: a ongoing problem that just escalated need ntl attention
 

Dont speak too soon there, still shows as an ongoing problem on the ntl site, Or has someone forgot to update it? :P

Re: a ongoing problem that just escalated need ntl attention
 

Don't get me started on the service status page :p

Re: a ongoing problem that just escalated need ntl attention
 

heh, hmmm the new hop has gone now and ms numbers shot back up justanothernoob they didnt roll back I hope?

check these I am not downloading or uploading.

Tracing route to tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
over a maximum of 30 hops:

1 21 ms 9 ms 15 ms 10.146.103.254
2 25 ms * 29 ms leic-t2cam1-a-ge96.inet.ntl.com [82.3.34.41]
3 38 ms 17 ms 33 ms leic-t2core-a-ge-210-0.inet.ntl.com [82.3.33.6]

4 33 ms 126 ms 91 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110]

5 90 ms 62 ms 13 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

6 39 ms 53 ms 44 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]


Trace complete.

Re: a ongoing problem that just escalated need ntl attention
 

status changed to green now

1 84 ms 152 ms 183 ms 10.146.103.254
2 112 ms 28 ms 38 ms leic-t2cam1-a-ge96.inet.ntl.com [82.3.34.41]
3 152 ms 116 ms 29 ms leic-t2core-a-ge-210-0.inet.ntl.com [82.3.33.6]

4 92 ms 12 ms 18 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110]

5 48 ms 23 ms 40 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

6 14 ms 139 ms 50 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
7 52 ms 62 ms 53 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

these are rising very high, its looking like the upgrade got pulled back.

Its not just traceroutes either, I have noticeable lag in ssh on several remote server's and some ssl websites have started to respond very slowly.

Re: a ongoing problem that just escalated need ntl attention
 

Fri, 23 Jul 2004 17:54:03 GMT
1st 128K took 3475 ms = 37719 Bytes/sec = approx 314 kbits/sec
2nd 128K took 3344 ms = 39196 Bytes/sec = approx 326 kbits/sec
3rd 128K took 3536 ms = 37068 Bytes/sec = approx 308 kbits/sec
4th 128K took 3695 ms = 35473 Bytes/sec = approx 295 kbits/sec

speedtest

Re: a ongoing problem that just escalated need ntl attention
 

UBR 10.146.103.254 at 2004 Jul 23, 19:16

Channel Freq Max Usage Users Min Ave Max
MHz kbps kbps ms ms ms
Dnstr 0 402.75 30342 10192 537 30 120 521
Upstr 1 18.0 2560 916 107 71 192 521
Upstr 2 20.0 2560 527 85 30 110 361
Upstr 3 22.0 2560 358 69 30 90 300
Upstr 4 24.4 2560 111 73 30 81 260
Upstr 5 26.4 2560 618 84 40 137 461
Upstr 6 28.4 2560 314 119 30 94 290

Ambit EuroDOCSIS Cable Modem 60549EU HW_Rev:1.9, SW_Rev:2.40.3225

System up time = 2 days 02h 32m 58.00s
Ethernet carrier sense xmit errs.1 = 259
Downstream channel ID = 0
Downstream channel frequency = 402750000 Hz
Downstream received signal power = -14.8 dBmV
Upstream channel ID = 1
Upstream channel frequency = 18000000 Hz
QoS max upstream bandwidth = 128000 bps
QoS max downstream bandwidth = 600000 bps
SigQu: Signal to Noise Ratio = 30.9 dB
Cable modem status = Operational
Upstream transmit signal power = 52.2 dBmV
Date and Time = 2004-07-23,18:49:16.0
Configuration filename = ntlhm120-silver.cm

I noticed I am on channel 1 which has a min ms of 72 double of all the other channels, I suspect there is an issue, can justanothernoob or another tech look into this? if not if I ring up reporting I used docsdiag to find a problem are they ok with it? also is my ubr scheduled to have the 5120 upstream upgrade?

Re: a ongoing problem that just escalated need ntl attention
 

Gissa MAC address monsieur (again) :p

Re: a ongoing problem that just escalated need ntl attention
 

sent

Re: a ongoing problem that just escalated need ntl attention
 

And sorted.

Re: a ongoing problem that just escalated need ntl attention
 

great work back to 10ms range

thanks again.

Re: a ongoing problem that just escalated need ntl attention
 

Nice one JustAnotherNoob :)