Ping help

Hey guys, I have a weird ping issue that I was hoping someone could figure out

I moved from AOL to Entanet via ADSL24 last March and my pings to the BBC/ADSL24 etc were in the late 20ms range. This lasted around a month before they inexplicably rose to 40ms+ and stayed there until I migrated to MurphX via ADSL24 on the 1st of February this year. My pings on MurphX were a solid 31ms but after a month they rose to 40ms+ again and have shown no signs of lowering.

Is there any reason why this would happen on my connection? Interleaving isn't enabled and I have no line issues (no packet loss, resyncs, line noise etc). It's not a big deal really but it is frustrating when my line suddenly starts performing a bit worse for no reason. I've asked around a fair bit but no-one seems to know why this is happening. James at ADSL24 has tried to help by changing my interleaving from Auto to Off but it didn't help unfortunately.

I'll post all the info I can about my connection here to help out (I'm sure I'll forget something though!)

Line Stats (the high UAS is because I forgot to plug my RJ11 cable back in straight away after upgrading the routers firmware the other day would the amount of other errors cause this ping issue? )
I use a Netgear DG834GT in modem only mode with a D-Link DIR-635 as a router (I've tried the DG834GT and my old DG834v3 by themselves without the DIR-635 but there was no difference)
I use a filtered faceplate with no extensions (I've tried other filters though)
I have a shielded RJ11 cable (again I've tried others though)
I'm on an Office ADSLMax package (its my only option, no LLU or 21CN in my exchange in Aberdeenshire )

Cheers in advance for reading and hopefully answering, if there's anything else you need to know ask away!

The high pings are probably caused by routing issues which are outside your control.

Try a tracert or traceroute (i.e. traceroute bbc.co.uk rather than ping bbc.co.uk) and try to identify how you are routed to the high ping destination.

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1

2 40 ms 42 ms 40 ms fe0-0-0.lns3.uan.rbm.uk.murphx.net [62.69.62.165]

3 40 ms 40 ms 41 ms ge0-3-1.er2.uan.rbm.uk.murphx.net [62.69.62.162]

4 42 ms 41 ms 40 ms ge2-6-1.cr1.core.rbm.uk.murphx.net [62.69.43.33]

5 40 ms 41 ms 40 ms ge0-0-1.tr1.core.rbm.uk.murphx.net [62.69.43.2]

6 40 ms 42 ms 42 ms gi4-3.ccr01.lon08.atlas.cogentco.com [149.6.146.89]

7 40 ms 40 ms 41 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.145]

8 42 ms 41 ms 41 ms ldn-b4-link.telia.net [213.248.70.237]

9 40 ms 42 ms 44 ms siemens-ic-124654-ldn-b4.c.telia.net [213.248.79.166]

10 42 ms 41 ms 42 ms 212.58.238.153

11 41 ms 41 ms 41 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Thanks for the reply I'm not entirely sure what those results mean or if they explain anything I pinged the BBC again too and they're 40ms exactly which is the best result I've had since early March \o/

Edited by Findlay (Tue 06-Apr-10 16:23:52)

You don't mention your o/s - but if you happen to be running windows - try pathping ( need to run cmd as admin )

Will show more detail on hops than tracert.

Regards - Zephya

C:\Windows\system32>pathping bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
0 Findlay [192.168.0.238]
1 192.168.0.1
2 fe0-0-0.lns3.uan.rbm.uk.murphx.net [62.69.62.165]
3 ge0-3-1.er2.uan.rbm.uk.murphx.net [62.69.62.162]
4 ge2-6-1.cr1.core.rbm.uk.murphx.net [62.69.43.33]
5 ge0-0-1.tr1.core.rbm.uk.murphx.net [62.69.43.2]
6 gi4-3.ccr01.lon08.atlas.cogentco.com [149.6.146.89]
7 te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.145]
8 ldn-b4-link.telia.net [213.248.70.237]
9 siemens-ic-124654-ldn-b4.c.telia.net [213.248.79.166]
10 212.58.238.153
11 virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Johnny-LP [192.168.0.238]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 44ms 0/ 100 = 0% 0/ 100 = 0% fe0-0-0.lns3.uan.rbm.uk.murphx.net
[62.69.62.165]
0/ 100 = 0% |
3 42ms 0/ 100 = 0% 0/ 100 = 0% ge0-3-1.er2.uan.rbm.uk.murphx.net
[62.69.62.162]
0/ 100 = 0% |
4 42ms 0/ 100 = 0% 0/ 100 = 0% ge2-6-1.cr1.core.rbm.uk.murphx.net
[62.69.43.33]
0/ 100 = 0% |
5 47ms 0/ 100 = 0% 0/ 100 = 0% ge0-0-1.tr1.core.rbm.uk.murphx.net
[62.69.43.2]
0/ 100 = 0% |
6 45ms 0/ 100 = 0% 0/ 100 = 0% gi4-3.ccr01.lon08.atlas.cogentco.c
om [149.6.146.89]
0/ 100 = 0% |
7 51ms 0/ 100 = 0% 0/ 100 = 0% te2-2.mpd01.lon01.atlas.cogentco.c
om [130.117.1.145]
0/ 100 = 0% |
8 46ms 0/ 100 = 0% 0/ 100 = 0% ldn-b4-link.telia.net [213.248.70.
237]
0/ 100 = 0% |
9 61ms 0/ 100 = 0% 0/ 100 = 0% siemens-ic-124654-ldn-b4.c.telia.n
et [213.248.79.166]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% 212.58.238.153
0/ 100 = 0% |
11 42ms 0/ 100 = 0% 0/ 100 = 0% virtual-vip.thdo.bbc.co.uk [212.58
.224.138]

Trace complete.

Is there anything untoward there?