![]() |
Shocking Ping
This is a tracert for a game2xs server and the admin said that it is down to me to contact ntl. I get a high ping in the server (120ms) whereas everyone else has good pings. I can't email this to NTL as i have never had a response from the in the past so don't expect help from them now. Can anyone shed some light? I get excellent connections to all other servers. I have reset my modem and my router. I shut down my linux server and apache. Only pc running was mine, still no joy. I have surfboard modem 1meg on ethernet. OS is XP pro
Tracing route to 217.161.41.44 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 192.168.0.1 2 10 ms 10 ms 9 ms 172.29.39.254 3 53 ms 22 ms 11 ms cdif-t2cam1-a-ge914.inet.ntl.com [62.254.254.37] 4 11 ms 42 ms 13 ms cdif-t2core-a-ge-wan61.inet.ntl.com [62.254.253. 33] 5 13 ms 12 ms 11 ms bir-bb-a-so-220-0.inet.ntl.com [213.105.172.45] 6 17 ms 13 ms 13 ms man-bb-b-so-700-0.inet.ntl.com [62.253.185.134] 7 15 ms 48 ms 15 ms man-bb-a-ae0-0.inet.ntl.com [62.253.187.177] 8 108 ms 106 ms 105 ms ycr2-so-3-0-0.Manchester.cw.net [208.175.252.89] 9 104 ms 111 ms 105 ms bcr2-so-3-0-0.Thamesside.cw.net [166.63.209.201] 10 105 ms 105 ms 108 ms iar1-loopback.Thamesside.cw.net [166.63.210.7] 11 109 ms 105 ms 110 ms rxtxtech-ltd.Thamesside.cw.net [166.63.217.10] 12 106 ms 108 ms 106 ms 217.161.41.44 Tracing route to rxtxtech-ltd.Thamesside.cw.net [166.63.217.10] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 9 ms 9 ms 11 ms 172.29.39.254 3 10 ms 11 ms 12 ms cdif-t2cam1-b-ge914.inet.ntl.com [62.254.254.165 ] 4 18 ms 36 ms 9 ms cdif-t2core-b-ge-wan62.inet.ntl.com [62.254.253. 169] 5 12 ms 59 ms 14 ms bre-bb-b-so-300-0.inet.ntl.com [213.105.172.49] 6 16 ms 16 ms 16 ms win-bb-a-so-400-0.inet.ntl.com [213.105.172.233] 7 102 ms 102 ms 102 ms bcr2-so-7-0-0.LND.cw.net [166.63.161.229] 8 102 ms 102 ms 132 ms bcr2-so-7-0-0.Thamesside.cw.net [166.63.209.205] 9 111 ms 102 ms 104 ms 206.24.168.97 10 103 ms 101 ms 102 ms rxtxtech-ltd.Thamesside.cw.net [166.63.217.10] |
Re: Shocking Ping
Looks absolutely fine until after it leaves the ntl network, 1st high pinging hop is:
7 102 ms 102 ms 102 ms bcr2-so-7-0-0.LND.cw.net [166.63.161.229] 8 108 ms 106 ms 105 ms ycr2-so-3-0-0.Manchester.cw.net [208.175.252.89] Seems ok here: 10 bcr1-so-2-0-0.Thamesside.cw.net (166.63.211.149) 20.487 ms 20.720 ms 18.221 ms 11 206.24.172.65 (206.24.172.65) 21.999 ms 19.465 ms 19.511 ms 12 rxtxtech-ltd.Thamesside.cw.net (166.63.217.10) 20.660 ms 23.026 ms 21.700 ms 13 217.161.41.44 (217.161.41.44) 21.701 ms 18.016 ms 19.506 ms |
Re: Shocking Ping
If you think its your connection, try pinging lifeless.aa.nu . The system on the end of that address is just on the network soley for ICMP pings.
|
Re: Shocking Ping
Oh and aa.nu are a UK ISP if your wondering. Returns an average latency of 15ms (thanks to a certain poster in the thread *cough*).
|
Re: Shocking Ping
Quote:
|
Re: Shocking Ping
Quote:
What does a traceroute back from the server to your PC look like? |
Re: Shocking Ping
Pinging lifeless.aa.nu [217.169.20.26] with 32 bytes of data:
Reply from 217.169.20.26: bytes=32 time=100ms TTL=45 Reply from 217.169.20.26: bytes=32 time=89ms TTL=45 Reply from 217.169.20.26: bytes=32 time=89ms TTL=45 Reply from 217.169.20.26: bytes=32 time=90ms TTL=45 Ping statistics for 217.169.20.26: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 89ms, Maximum = 100ms, Average = 92ms This is what i get from the ping. pretty dismal by the looks |
Re: Shocking Ping
Notes Manchester - thinks, Broadband is fooked up there right now.
Aint it? |
Re: Shocking Ping
Might be worth keeping a sticky at the top for overloaded NTL area's.
Problem is, it may only effect 1/3 - 1/6th of the user base and may drive potential "customers" away. |
Re: Shocking Ping
Quote:
The IP addresses maybe look American but that's probably because Cable and Wireless are American and a global company and cannot always allocate blocks of addresses to certain areas. :erm: The site seems fine here . . Microsoft Windows 2000 [Version 5.00.2195] (C) Copyright 1985-2000 Microsoft Corp. E:\Documents and Settings\Administrator>tracert 217.161.41.44 Tracing route to 217.161.41.44 over a maximum of 30 hops 1 3405 ms 10 ms 20 ms 10.34.112.1 2 20 ms 10 ms 20 ms herm-t2cam1-b-ge96.inet.ntl.com [80.3.34.157] 3 150 ms 201 ms 200 ms herm-t2core-a-ge-wan61.inet.ntl.com [80.3.33.5] 4 10 ms 20 ms 10 ms pop-bb-b-so-210-0.inet.ntl.com [62.253.187.21] 5 20 ms 20 ms 20 ms lee-bb-a-so-700-0.inet.ntl.com [62.253.185.237] 6 20 ms 20 ms 20 ms lee-bb-b-ae0-0.inet.ntl.com [62.253.187.186] 7 10 ms 20 ms 20 ms man-bb-a-so-700-0.inet.ntl.com [62.253.185.193] 8 20 ms 20 ms 31 ms ycr2-so-3-0-0.Manchester.cw.net [208.175.252.89] 9 30 ms 20 ms 10 ms iar1-loopback.Thamesside.cw.net [166.63.210.7] 10 30 ms 30 ms 10 ms rxtxtech-ltd.Thamesside.cw.net [166.63.217.10] 11 30 ms 20 ms 20 ms bcr2.London.cw.net [166.63.162.62] 12 20 ms 20 ms 20 ms bcr2-so-7-0-0.Thamesside.cw.net [166.63.209.205] 13 30 ms 20 ms 20 ms 217.161.41.44 Trace complete. Can't say the same for the ntl network though - 3405ms is extremely high :erm: :shocked: |
Re: Shocking Ping
Actually I'm thinking that packets are taking a different route back to the one they took outgoing, that's why the transatlantic trip doesn't show.
re: pings - I'd check your stateful firewall or the load on your connection when you did that traceroute, 3405ms -> 10ms -> 20ms is not the ntl network ;) |
Re: Shocking Ping
Quote:
|
Re: Shocking Ping
Quote:
personally i find kerio heaps better :) |
Re: Shocking Ping
i have been in contact with NTL and after 30 minutes they said that i have to contact cable and wireless (corporate side) to get it sorted. Now does this sound right. Why can't they re-route me? Why can't they sort it out with CW. I feel they fobbed me off. Not like the server i play in is a random one. It's our monthly rented games server and i'm the only person with problems.
|
Re: Shocking Ping
Quote:
|
| All times are GMT. The time now is 16:08. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum