Pings and traceroutes

[_ST]

Hi, still getting really bad pings between 4pm and midnight anytime before or after this time get a ping of 20 -30. So i ring VM and eventually after saying that there is no problem with the network i say shall i send a traceroute.

So i now send the traceroute and the lady from india clearly has not bothered to even look at it, as another CS rep tells me.

Anyway VM look at the traceroute and tell me that even tho the numbers get up into the 200s that it does not mean it is there fault as it has left the VM server. He then said i should contact the gaming server. he states even though it hits 70 on ntl server that is fine, well guess what it aint it jumps to that peak and makes gaming nearly impossible, and for the rest of the year it has been 20-30 even on massivley crowded servers so it is not acceptable to me.

I have tried over 30 servers and i always get a high ping. So can all the 30 plus servers be screwed up, if that was the case everyone on that server would surely get bad pings too?

http://homepage.ntlworld.com/l.bunton/tracert2.JPG

I get this every year for the last for years and was told last year that it was oversubscription to an UBR.

I am about to give up as why pay for a service that i cannot use properley.

:mad:

[blade85]

Iv just done a trace to that same IP and my results are much better, so there is definitely something wrong with your connection.

https://www.cableforum.co.uk/images/local/2007/05/21.jpg

[Sherlock614]

I had this a while back to another gaming server.

I was told that is was the routers fault (in Telehouse). It is not set to be pinged, so sends a high result back (something like that). But your ping on the hops after it are ok. (In other words nothing to worry about).

I had exactly the same a couple of years ago, resulting in more than a few calls to NTL techs.

Edit, didn't see this bit sorry.

I have tried over 30 servers and i always get a high ping. So can all the 30 plus servers be screwed up, if that was the case everyone on that server would surely get bad pings too?

[Paul]

Hi, still getting really bad pings between 4pm and midnight anytime before or after this time get a ping of 20 -30. So i ring VM and eventually after saying that there is no problem with the network i say shall i send a traceroute.Two out of three on that trace are 17ms and 18ms - not much of a problem there. The other was a bit worse at 37ms.

A better test in this case would be a sustained couple of hundred pings, to see if there is an intermittant problem.

[Sherlock614]

I am also getting 200ms on that hop in Telehouse.



8 15 ms 22 ms 12 ms nth-bb-b-so-100-0.inet.ntl.com [62.253.185.101]

9 34 ms 45 ms 72 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
10 186 ms 200 ms 29 ms 212.250.14.110
11 30 ms 30 ms 31 ms te4-1.telehouse-north.core.enta.net [87.127.236.
38]
12 18 ms 45 ms 16 ms 62-249-255-186.no-dns-yet.enta.net [62.249.255.1
86]
13 52 ms 14 ms 32 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
14 24 ms 14 ms 23 ms 81.19.208.13

---------- Post added at 23:04 ---------- Previous post was at 22:53 ----------

Also, a great little prog i use for checking pings / routes to servers (rather than command prompt), is Winmtr.

http://sourceforge.net/projects/winmtr

[homealone]

05/22/07 23:07:18 Fast traceroute 81.19.208.13
Trace 81.19.208.13 ...
1 192.168.1.1 0ms 0ms 0ms TTL: 0 (No rDNS)
2 10.249.136.1 8ms 9ms 9ms TTL: 0 (No rDNS)
3 82.13.48.65 14ms 12ms 11ms TTL: 0 (nott-t2cam2-a-v613.inet.ntl.com ok)
4 195.182.175.129 14ms 30ms 15ms TTL: 0 (nott-t3core-1a-ge-110-0.inet.ntl.com ok)
5 213.105.174.169 15ms 20ms * TTL: 0 (lee-bb-a-so-020-0.inet.ntl.com ok)
6 62.253.185.101 39ms 42ms 14ms TTL: 0 (nth-bb-b-so-100-0.inet.ntl.com ok)
7 62.253.184.2 46ms 23ms 21ms TTL: 0 (tele-ic-1-as0-0.inet.ntl.com ok)
8 212.250.14.110 34ms 34ms 35ms TTL: 0 (No rDNS)
9 87.127.236.38 47ms 36ms 59ms TTL: 0 (te4-1.telehouse-north.core.enta.net ok)
10 62.249.255.186 17ms 18ms 20ms TTL: 0 (62-249-255-186.no-dns-yet.enta.net probable bogus rDNS: No DNS)
11 217.146.81.254 27ms 18ms 19ms TTL: 0 (sov-r1-rtr1.4u.net.uk ok)
12 81.19.208.13 21ms 19ms 18ms TTL: 55 (No rDNS)

[_ST]

Although the traceroute does not show sustained high numbers it really is making my ping go well over 100 at night yet in the morning my pings are 20-40 in any server i go in, so something is a miss. Unfortunately i have had this every year for the last four years just a bit fed up with it now. Vm do not seem to want to help so i cannot do anything.

You should see the hassle i have had with tech support lol especially the India call centre man they are hard work.

[r00t]

1: cpc3-brmb4-0-0-cust972.bagu.cable.ntl.com (80.removed.my.IP) 0.393ms pmtu 1500
1: 10.137.156.1 (10.137.156.1) 11.966ms
2: bagu-t2cam1-b-v138.inet.ntl.com (80.5.163.209) 13.822ms
3: bagu-t2core-b-ge-wan63.inet.ntl.com (195.182.175.33) 12.034ms
4: lee-bb-b-so-710-0.inet.ntl.com (213.105.174.73) asymm 5 15.493ms
5: nth-bb-a-so-600-0.inet.ntl.com (213.105.175.133) 17.584ms
6: nth-bb-b-so-200-0.inet.ntl.com (213.105.172.194) 44.266ms
7: tele-ic-1-as0-0.inet.ntl.com (62.253.184.2) asymm 8 19.402ms
8: 212.250.14.110 (212.250.14.110) asymm 12 36.888ms
9: te4-1.telehouse-north.core.enta.net (87.127.236.38) asymm 11 25.769ms
10: 62-249-255-186.no-dns-yet.enta.net (62.249.255.186) asymm 11 19.244ms
11: sov-r1-rtr1.4u.net.uk (217.146.81.254) asymm 12 22.347ms
12: 81.19.208.13 (81.19.208.13) asymm 14 20.036ms reached
Resume: pmtu 1500 hops 12 back 14
r00t@valium:~$


And its night now, and I'm with VM ex-ntl.
Do another tracert now mate, please.

[homealone]

1: cpc3-brmb4-0-0-cust972.bagu.cable.ntl.com (80.removed.my.IP) 0.393ms pmtu 1500
1: 10.137.156.1 (10.137.156.1) 11.966ms
2: bagu-t2cam1-b-v138.inet.ntl.com (80.5.163.209) 13.822ms
3: bagu-t2core-b-ge-wan63.inet.ntl.com (195.182.175.33) 12.034ms
4: lee-bb-b-so-710-0.inet.ntl.com (213.105.174.73) asymm 5 15.493ms
5: nth-bb-a-so-600-0.inet.ntl.com (213.105.175.133) 17.584ms
6: nth-bb-b-so-200-0.inet.ntl.com (213.105.172.194) 44.266ms
7: tele-ic-1-as0-0.inet.ntl.com (62.253.184.2) asymm 8 19.402ms
8: 212.250.14.110 (212.250.14.110) asymm 12 36.888ms
9: te4-1.telehouse-north.core.enta.net (87.127.236.38) asymm 11 25.769ms
10: 62-249-255-186.no-dns-yet.enta.net (62.249.255.186) asymm 11 19.244ms
11: sov-r1-rtr1.4u.net.uk (217.146.81.254) asymm 12 22.347ms
12: 81.19.208.13 (81.19.208.13) asymm 14 20.036ms reached
Resume: pmtu 1500 hops 12 back 14
r00t@valium:~$


And its night now, and I'm with VM ex-ntl.
Do another tracert now mate, please.

do you mean me?



05/22/07 23:40:26 Fast traceroute 81.19.208.1
Trace 81.19.208.1 ...
1 192.168.1.1 0ms 0ms 0ms TTL: 0 (No rDNS)
2 10.249.136.1 13ms 8ms 8ms TTL: 0 (No rDNS)
3 82.13.48.65 12ms 24ms 17ms TTL: 0 (nott-t2cam2-a-v613.inet.ntl.com ok)
4 195.182.175.129 14ms 14ms 11ms TTL: 0 (nott-t3core-1a-ge-110-0.inet.ntl.com ok)
5 213.105.174.169 13ms 34ms 17ms TTL: 0 (lee-bb-a-so-020-0.inet.ntl.com ok)
6 62.253.185.101 14ms 21ms 20ms TTL: 0 (nth-bb-b-so-100-0.inet.ntl.com ok)
7 62.253.184.2 20ms 28ms 20ms TTL: 0 (tele-ic-1-as0-0.inet.ntl.com ok)
8 212.250.14.110 44ms 35ms 37ms TTL: 0 (No rDNS)
9 87.127.236.38 34ms 41ms 36ms TTL: 0 (te4-1.telehouse-north.core.enta.net ok)
10 62.249.255.186 18ms 21ms 52ms TTL: 0 (62-249-255-186.no-dns-yet.enta.net probable bogus rDNS: No DNS)
11 81.19.208.1 22ms 20ms 30ms TTL:247 (No rDNS)

[Down the Pub]

you can try this to look at sustained pings over a period...not bad for a freebie

Ping Plotter (http://www.download.com/Ping-Plotter-Freeware/3000-2085_4-10172484.html)

[r00t]

Thanks homealone, from our traces, I fail to see how this could be a routing issue.
@ Down the Pub, great aplication. I use that on my *( hangs head in shame)* windows PC.

[Mcshane123]

It is a fault with Virgin Medias network i have exactly the same problem, peak/busy hours pings are a joke & unplayable, where as other times they are okay. They just won't admit it's a problem at their end and even if they do they won't do anything about it. I've sent numerous complaints with tracerts at different times, prooving it's their problem but i never get a reply.

Change ISP's thats what i plan on doing v.soon

[Chris W]

Is it a fault with VM's network? Have you got any proof?

*sigh* I really wish that people would understand what they are posting before making accusations of who is at fault.

A good starting point for understanding what a traceroute actually means:
http://www.chetnet.co.uk/articles/index.php?page=index_v2&id=29&c=5

[Sherlock614]

"...things to be aware of, first and most important is that not all routers or web sites respond to icmp traffic and you may see timeouts which do not necessarily indicate a problem".

Thanks Chris, that's what i meant :)

[tweetiepooh]

Also ICMP traffic is regarded as less important so may be dropped and/or delayed by device(s). Good for your IP traffic, maybe less so for some games.