NTL playing up yet again

[darbey]

Is it so ffin dificult for these baboons at NTL to keep a decent connection .
Sure we went through all the same hassle a fortnight ago

see thread below

http://forums.barrysworld.com/showthread.php?s=&threadid=57468&perpage=25&pagenumber=1

Any one else got same prob from ntl in particular North east?

Host Information
1, -------------- ,172.21.215.254
2,midd-t2cam1-b-ge-wan41-106.inet.ntl.com,213.106.238.165
3,mid-t2core-b-ge-wan61.inet.ntl.com,213.106.237.161
4,ren-bb-b-so-220-0.inet.ntl.com,62.253.187.93
5,man-bb-a-so-600-0.inet.ntl.com,62.253.185.170
6,man-bb-b-ge-221-0.inet.ntl.com,62.253.187.178
7, -------------- ,213.206.159.245
8,sl-bb20-lon-11-0.sprintlink.net,213.206.128.56
9,sl-bb21-par-14-0.sprintlink.net,213.206.129.70
10,sl-gw10-par-15-0.sprintlink.net,217.118.224.42
11,sle-franc1-1-0.sprintlink.net,213.206.131.42
12,P13-0.PASCR2.Pastourelle.opentransit.net,193.251.241.169
13,P11-0.PASCR1.Pastourelle.opentransit.net,193.251.241.97
14,P4-0.BAGCR3.Bagnolet.opentransit.net,193.251.241.118
15,P1-0.BAGBB1.Bagnolet.opentransit.net,193.251.241.145
16,WanadooPortails1.GW.opentransit.net,193.251.251.58
17, -------------- ,193.252.122.10
18, -------------- ,193.252.123.33

Sample Information
"12/05/2003 16:59:53",31,9,11,30,19,18,25,29,35,*,69,48,32,36,40,31,*,55
"12/05/2003 17:00:03",14,76,62,43,34,32,32,*,33,31,*,40,89,65,64,*,37,33
"12/05/2003 17:00:13",7,8,10,13,19,49,41,43,*,*,30,*,84,*,*,36,36,59
"12/05/2003 17:00:23",8,12,10,13,16,18,23,*,61,*,*,31,31,35,31,34,*,39
"12/05/2003 17:00:33",10,46,31,51,57,49,41,*,55,*,53,31,53,*,57,35,*,*
"12/05/2003 17:00:43",65,43,28,34,36,50,42,24,*,*,31,31,35,40,*,49,*,35
"12/05/2003 17:00:53",33,9,84,17,19,23,70,46,*,41,38,34,33,*,47,33,33,77
"12/05/2003 17:01:03",7,9,8,19,20,17,26,27,31,32,*,*,34,33,37,33,*,45
"12/05/2003 17:01:13",7,8,8,74,66,39,33,30,32,*,34,65,61,37,74,49,36,34

 

[tris-]

yep same shit problem as before, just glad i dont play anymore and dont have to go through the crap to get it fixed again.

edit: cos of 4,ren-bb-b-so-220-0.inet.ntl.com,62.253.187.93
btw, for some shit reason they changed the routing.

 

[Vorcyn]

Planned Maintenance w/c 12/5/03
As part of the ongoing project to upgrade the existing Broadband network, there is a requirement to carry out Universal Broadband Router or uBR upgrades, and maintenance to the core network.

In order to implement a minor configuration change to the uBRs there will be a short outage to customers in the following areas on the 13/5/03 between 01:00 and 05:00 :- Northfields, Stapleford, Reading, Shepshed, Stockton and Birmingham.

In order to implement a minor configuration change to the DHCP servers there will be a short outage to customers in the Leicester and Nottingham areas on the 13/5/03 between 01:00 and 05:00.

Amalgamation of public IP address ranges at the Blackburn, Bolton, Brighton, Bromley, Charminster, Cosham, Derby and Epsom sites may result in a loss of service to customers in these areas until a new IP address is leased (reboot of PC will resolve) on the 13/5/03 at 01:00 to 05:00.

Amalgamation of public IP address ranges at the Harrogate, Hersham, Lancing, Leeds, Macclesfield, Oldham and Pool sites may result in a loss of service to customers in these areas until a new IP address is leased (reboot of PC will resolve) on the 14/5/03 at 01:00 to 05:00.

Amalgamation of public IP address ranges at the Reigate, Salford, Seven Kings, Southampton, Waltham Park, Wearside, Withington and York sites may result in a loss of service to customers in these areas until a new IP address is leased (reboot of PC will resolve) on the 15/5/03 at 01:00 to 05:00.

uBR resegmentation in the Portsmouth area will result in a loss of service for some customers in this area on the 15/5/03 between 01:00 and 05:00.

Please accept our apologies for any inconvenience this may cause.

Are you part of that?

Always check here first for ntl related problems: http://www.ntl-isp.ntl.com/lookup/default.asp

 

[tris-]

stockton area will effect all over the place so it must be that.

 

[Sharma]

ah well, ive stopped playing for a bit, guess its gonna be quite a whilke before they sort it out appropriately

 

[darbey]

The outtage was supposedly between 0100 and 0500 this morning. This has just started happening about 4pm

No doubt cos theyve changed something again.

 

[darbey]

mods can u please sticky this again please till we can ascertain extent of problem

thanks

 

[old.Nikolas]

Teesside down again

Same old as before

 

[darbey]

u got probs also nikolas?

 

[FredaOfAxiom]

Same for me too.. I live in Redcar .. Hummm time to moves ISP's uke:

 

[darbey]

Have spoken with NTL, please send your trace routes, pings, ping plotter text files to james6200@ntlworld.com so they can diagnose and hopefully fix the problem.

 

[civy]

Originally posted by darbey


Any one else got same prob from ntl in particular North east?

Not the north east. But Oldham is down again

 

[The Kingpin]

Getting massive lag,

Not link dead, about 8 second delay..

Am on Broadband, but not NTL..

 

[darbey]

Please contact NTL , more we raise this more chance they will take note

Thanks

Always happens on my ffin week off.

N3wbie guess we need your help again 8) Go get em

 

[Gerta Ugbash]

Aye Same again

Glad I kept the Mobile Number of NTL's Northwest Internet Operations manager. 8pm and still answered his mobile well impressed. He's gonna contact good old Dave tonight, if not he's on the case tomorrow. :great:

Time to Shoot some on America's Army

edit: Nerf Typos!!!

 

[Gerta Ugbash]

There on the case already it seems.

My Firewalls just hit the roof as they send thier test pings to my machine (Recognise the addresses and ports from last time... I know sad isn't it)

Anyway hopefully they can sort it out sharpish (And for good not the old Blue Peter Sticky back plastic approach) and I can get back to levelling my Spiritmaster.

 

[civy]

Sent my treceroute to ntl and this is what they say


"Looking at the tracert that have been sent in the dropped packets are coming on sprintlink.net network and not on the ntl network.
unfortunately you would need to contact them re this packet loss and not ntl."

Any idea who at sprint i should contact?

 

[Gerta Ugbash]

Looks like you got an NTL n00b

From your Tracert it looks like your loosing packets on sprintlink, however this is because the NTL routers are loosing the packets.

If you perform a backtrace from Sprintlink or similar they will show the packets being lost on the NTL Routers.

try pinging back from opentransit at -
http://www.opentransit.net/lg.htm
put router as pastourelle-backbone1
click trace and put your IP.
This is what I get

Type escape sequence to abort.
Tracing the route to public1-oldhx-3-cust50.oldh.broadband.ntl.com (213.106.xxx.xxx)

1 P4-0.PASCR3.Pastourelle.opentransit.net (193.251.241.162) 0 msec 0 msec 0 msec
2 P9-0.PASCR1.Pastourelle.opentransit.net (193.251.129.61) 0 msec 0 msec 0 msec
3 Level.GW.opentransit.net (193.251.240.214) 0 msec 0 msec 0 msec
4 ae0-15.mp1.Paris1.Level3.net (212.73.240.65) [AS 3356] 4 msec 0 msec 0 msec
5 so-3-0-0.mp1.London2.Level3.net (212.187.128.46) [AS 3356] 8 msec 12 msec 8 msec
6 pos4-0.hsipaccess1.London2.Level3.net (212.187.129.250) [AS 3356] 12 msec 8 msec 8 msec
7 195.50.116.134 [AS 3356] 8 msec 12 msec 8 msec
8 win-bb-a-so-400-0.inet.ntl.com (213.105.172.233) [AS 5089] 12 msec 12 msec 12 msec
9 man-bb-b-so-600-0.inet.ntl.com (62.253.185.137) [AS 5089] 12 msec 12 msec 16 msec
10 man-t2core-b-pos31.inet.ntl.com (62.253.184.62) [AS 5089] 144 msec 200 msec 52 msec <---- Suspect IMO
11 oldh-t2cam1-b-ge-wan31.inet.ntl.com (213.104.242.170) [AS 5089] 20 msec 16 msec 16 msec
12 ubr03oldh-ge20.inet.ntl.com (80.5.164.138) [AS 5089] 40 msec 16 msec 48 msec

an look who the suspect one belongs to hmmm

I'm not 100% on this but I've contacted as high as you get in NTL's internet operations and they are aware.

/em Fiddles Thumbs

 

[spydor]

Yeh also getting the same problems here - also in the North East - have sent plots to ntl already!

 

[sheepseyes]

dont think it was just ntl im on bt and suffered ld and major lag for bout 2hrs

 

[darbey]

Bump ,still totally unplayable

 

[darbey]

Ntl are so reluctant to investigate this as from a tracert it looks like your loosing packets on sprintlink and opentransit , however this is because the NTL routers are loosing the packets.

As Gerda explained previously if you perform a backtrace from Sprintlink or similar they will show the packets being lost on the NTL Routers.

try pinging back from opentransit at -
http://www.opentransit.net/lg.htm
put router as pastourelle-backbone1 (This is last router between us and the euro daoc server)
click trace and put your IP.

And hey presto its apparant who indeed has the problem - NThell

I have spoken at length to net admins at opentransit and in brief to one from sprint link who both confirmed same results.

This is what mine shows

OPENTRANSIT Looking Glass Results


--------------------------------------------------------------------------------


Query: trace
Router: pasbb1.opentransit.net
Addr: xx.xxx.xx.77


trace xx.xxx.xx.77

Type escape sequence to abort.
Tracing the route to xxx-hart2-3-cust77.midd.cable.ntl.com (xx.xxx.xx.77)

1 P4-0.PASCR3.Pastourelle.opentransit.net (193.251.241.162) 4 msec 0 msec 0 msec
2 P9-0.PASCR1.Pastourelle.opentransit.net (193.251.129.61) 0 msec 0 msec 0 msec
3 Level.GW.opentransit.net (193.251.240.214) 4 msec 0 msec 0 msec
4 ae0-11.mp1.Paris1.Level3.net (212.73.240.1) [AS 3356] 0 msec 4 msec 0 msec
5 so-1-0-0.mp2.London2.Level3.net (212.187.128.42) [AS 3356] 8 msec 8 msec 8 msec
6 pos5-0.hsipaccess1.London2.Level3.net (212.187.129.254) [AS 3356] 8 msec 12 msec 8 msec
7 195.50.116.134 [AS 3356] 8 msec 8 msec 12 msec
8 ren-bb-a-so-100-0.inet.ntl.com (62.253.185.165) [AS 5089] 20 msec 20 msec 20 msec
9 ren-bb-b-ge-720-0.inet.ntl.com (62.253.185.186) [AS 5089] 20 msec 20 msec *
10 mid-t2core-b-pos31.inet.ntl.com (62.253.187.94) [AS 5089] 24 msec * 24 msec
11 *
midd-t2cam1-b-ge-wan31.inet.ntl.com (213.106.237.162) [AS 5089] 24 msec *
12 midd-hart-ubr-2-ge20.inet.ntl.com (213.106.238.166) [AS 5089] 24 msec 24 msec 24 msec
13 pc4-hart2-3-cust77.midd.cable.ntl.com (xx.xxx.xx.77) [AS 5089] 68 msec 32 msec *
PASBB1>

NB Own ip edited out

 

[Gerta Ugbash]

Wahay got a phone call this morning before I set of for work From ntl_support himself. Managed to rush off a couple of Tracerts to him before I came to work, but only one of the two showed real errors.

Hopefully they'll have it fixed for when I get home

 

[acei]

I'm on NTL and am having no problems at all, i'm in North West (i was effected the last time NTL had problems with DAOC)

 

[kuragari]

I would address this from the inside but this problem hasn't effected the Wales area yet... which is where I am based. NTL works fine here, even on dial-up.

Hope you get your problem fixed. Just a few basic rules when you're talking to NTL Tech Support:

1) NEVER mention that you can't play your games, we will give you 1 line: "We do not support games" *click*

2) More than likely, you will get a n00bie agent - they have no clue. Keep ringing and sending mails. Eventually you will get a veteran agent.

3) Be prepared - Do your traceroutes etc before you call - anything that will keep you silent for about 30 seconds the agent will say: "try that, and call back when you're done." *click*

4) Don't shout, scream, kick a fuss. We're people too. Well... some of us.

 

[darbey]

Thanks to dave muirhead at NTL once again. Quick resolution this time.

Shame they cant train the phone monkeys to assist in this rather than having to contact the net admins ourselves.

 

[Gerta Ugbash]

Nice one

Cheers once again Dave

 

[civy]

FFS it's gone again

 

[darbey]

yep me too again ld every few mins and 8-10 sec lags

 

[Sharma]

worse this time, my entire internet has gone kaputt, this post i think will take about 3 mins to post :\