High pings to London server.

[James Henry]

There's loads of weird routing if you look for it.

Think there's a fair bit of traffic engineering going on both inside and outside their network, for example:

7 8 ms 8 ms 7 ms so-1-2-0.gar2.London1.Level3.net [212.113.0.118]

8 8 ms 8 ms 8 ms sl-bb21-lon-6-0.sprintlink.net [213.206.131.21]

9 8 ms 8 ms 8 ms sl-gw11-lon-15-0.sprintlink.net [213.206.128.59]

10 10 ms 10 ms 9 ms sle-ntl-5-0.sprintlink.net [213.206.156.102]
11 11 ms 11 ms 11 ms win-bb-a-so-500-0.inet.ntl.com [213.105.172.129]

Even though ntl have a link to Level3 directly traffic goes over Sprint when destined to some of their network.

Excuse the pings by the way, wireless adds a ms or 2

[jtwn]

Oh noes... a millisecond

[Florence]

Originally Posted by Neil

Why the shocked face?

Perhaps because after 6 yrs I have never had pings so bad for as long..

Tonight again the server keeps kicking me and its due to NTL and the messed up network. There is no chance the way NTL are managing this network or perhaps the lack of managment they expect the network run like a well oiled machine when they havent the staff to keep it oiled.

Tonights pings

Tracing route to 212.187.246.186 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms WRT54GS [192.168.1.1]
2 9 ms 6 ms 8 ms 10.9.0.1
3 478 ms 124 ms 13 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
4 445 ms 9 ms 19 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
5 178 ms 295 ms 299 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

6 158 ms 271 ms 302 ms dbln-bb-b-so-700-0.inet.ntl.com [213.105.174.46]

7 451 ms 292 ms 287 ms dbln-bb-a-ae0-0.inet.ntl.com [213.105.174.50]
8 373 ms 278 ms 280 ms 213.242.106.37
9 291 ms 287 ms 276 ms so-4-1-0.bbr1.london1.level3.net [4.68.128.113]

10 467 ms 322 ms 464 ms ge-10-1.ipcolo2.london1.level3.net [4.68.116.74]

11 * 97 ms 270 ms 212.187.246.186

Trace complete.

---------- Post added at 22:55 ---------- Previous post was at 22:20 ----------

Well what a wonderful wait started waiting at 10.25pm with 70 people ahead of me.. India call center I explained about the network and how my end was fine and others not on NTL say the server is fine it's the naff network I am on connecting me to the server. She insist I have to phone a different number if its for games!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Doesn't other people not play games on PC's online I never mentioned a console we dont connect a console to the network its the PC they play online games with and she gives me 0845 650 0101 I have wasted almost 30 mins put my phone bill higher and for nothing as there is nothing being done about it.

---------- Post added at 23:18 ---------- Previous post was at 22:55 ----------

two calls to tech support and again if you remove the router the pings will be better its the firewall on the router
1 <1 ms <1 ms <1 ms WRT54GS [router]
2 9 ms 6 ms 8 ms SACM
3 478 ms 124 ms 13 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
4 445 ms 9 ms 19 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]NTLS network

No chance the router is doing anything

[James Henry]

I've been informed that http://www.cableforum.co.uk/board/sh...71&postcount=5 is closest to the truth, ntl are having problems with their Juniper core routers and aggregated interfaces.

Not the first time.

[Florence]

Originally Posted by James Henry

I've been informed that http://www.cableforum.co.uk/board/sh...71&postcount=5 is closest to the truth, ntl are having problems with their Juniper core routers and aggregated interfaces.

Not the first time.

Thank you for the link I had been doing some tests in mIRC and the results given was that someone was raping the upload. I am on 2mb and the connection has been going downhill fast its fine by day when everyone is at work then around tea pings go high and that is it till gone 2am.

As for phoning Tech support as customers we was told teh India call center was to stop queues on the line its no different except NTL plan to rape your bank balance for calling them. I was on twice last night the first was a total waste of time the second a little more helpful at least he did escalate it or said he had only time will tell. On the 0870 number my calls last night would cost me first one £2.16 the second one £1.96 now that is highway robbery.

---------- Post added at 11:35 ---------- Previous post was at 10:37 ----------

Just to prove its upload contention I have completed another tracer route this morning

Tracing route to 212.187.246.186 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms WRT54GS [192.168.**.***]
2 7 ms 9 ms 8 ms 10.9.0.1
3 9 ms 7 ms 7 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
4 9 ms 24 ms 11 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
5 9 ms 9 ms 9 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

6 20 ms 30 ms 13 ms dbln-bb-b-so-700-0.inet.ntl.com [213.105.174.46]

7 12 ms 20 ms 13 ms dbln-bb-a-ae0-0.inet.ntl.com [213.105.174.50]
8 19 ms 11 ms 12 ms 213.242.106.37
9 34 ms 21 ms 19 ms so-4-1-0.bbr1.london1.level3.net [4.68.128.113]

10 24 ms 18 ms 20 ms ge-10-2.ipcolo2.london1.level3.net [4.68.116.138
]
11 19 ms 42 ms 19 ms 212.187.246.186

Trace complete.

this changes as evening arrives,

[James Henry]

Originally Posted by Florence

Just to prove its upload contention I have completed another tracer route this morning

Nope you misunderstand it's not upstream contention it's a fault with the routers themselves and how they are handling traffic, not a shortage of bandwidth.

The traces you've put in post 18 prove no issues with contention, the hope after your router is ntl's network not your cable modem.

[Chrysalis]

Well if its a fault of some sort it has caused them to make my routing better.

I did another trace and still going direct to london, since this issue cropped up my speeds in the evening have gone from 50-150kB to 500-900kB.

So please when you fix this ntl leave Leics routing how it is right now.

[Florence]

to who ever sorted out my pings problem.

Tracing route to 212.187.246.186 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms WRT54GS [192.168.**.***]
2 9 ms 18 ms 7 ms 10.9.0.1
3 18 ms 8 ms 8 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
4 8 ms 10 ms 8 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
5 9 ms 9 ms 12 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

6 9 ms 9 ms 7 ms man-bb-a-ae0-0.inet.ntl.com [62.253.187.177]
7 8 ms 8 ms 21 ms 212.187.137.1
8 9 ms 10 ms 12 ms so-6-1-0.mp2.manchesteruk1.level3.net [4.68.113.
118]
9 15 ms 15 ms 15 ms so-1-1-0.bbr1.london1.level3.net [4.68.128.73]
10 15 ms 16 ms 15 ms ge-11-1.ipcolo2.london1.level3.net [4.68.116.106
]
11 34 ms 43 ms 15 ms 212.187.246.186

Trace complete.

thank you guys now I can have a game of CS and not get shot before I move.

[Chrysalis]

thank god someone listened still going direct to london

[Druchii]

Originally Posted by Florence

to who ever sorted out my pings problem. thank you guys now I can have a game of CS and not get shot before I move.

I know the feeling

[Florence]

Well this fix was short lived

Tracing route to 212.187.246.186 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms WRT54GS [192.168.**.***]
2 167 ms 181 ms 189 ms 10.9.0.1
3 311 ms 196 ms 240 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
4 192 ms 205 ms 215 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
5 268 ms 219 ms 201 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]

6 311 ms 314 ms 315 ms man-bb-a-ae0-0.inet.ntl.com [62.253.187.177]
7 233 ms 211 ms 215 ms 212.187.137.1
8 330 ms 210 ms 257 ms so-6-1-0.mp2.manchesteruk1.level3.net [4.68.113.
118]
9 173 ms 213 ms 210 ms ae-1-0.bbr2.london1.level3.net [212.187.128.57]

10 289 ms 222 ms 200 ms ge-11-0.ipcolo2.london1.level3.net [4.68.116.42]

11 293 ms 265 ms 212 ms 212.187.246.186

Trace complete.

Pinging 212.187.246.186 with 32 bytes of data:

Reply from 212.187.246.186: bytes=32 time=187ms TTL=53
Reply from 212.187.246.186: bytes=32 time=185ms TTL=53
Reply from 212.187.246.186: bytes=32 time=206ms TTL=53
Reply from 212.187.246.186: bytes=32 time=220ms TTL=53

Ping statistics for 212.187.246.186:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 220ms, Average = 199ms

[jtwn]

Look where your pings are highest first. A uBR should not return pings like that. Its a different problem.

[Chrysalis]

that ubr latency is unreal, either the ubr has a problem congestion or fault, or you have a problem at your pc/modem maybe running torrents maxed out.

[James Henry]

Are you sure that you're the only person using the connection at the time these were taken?

I see a router in there before the ntl network so isn't it possible that one of your family is uploading or downloading?

[Florence]

Originally Posted by Chrysalis

that ubr latency is unreal, either the ubr has a problem congestion or fault, or you have a problem at your pc/modem maybe running torrents maxed out.

I havent any torrent software on my PC and if my son had been home then I wouldnt be so sure but he was away at his mates where he has been since thursday. infact I never have and wouldnt know where to start to look for any.


I do not download any torrant things the od linux iso or any software I buy that is downloadable, I occasionally listen to a radio stream.. modem is working fine