Intermittant high ping (google.co.uk > 2000ms)

[psmith98752]

Hi Guys

Literally don't know whats up here any more. Randomly (i'd say every 10mins), pings get very high, eg google.co.uk 2000-3000ms, some timing out. This lasts at least 5 mins before the pings gradually go back to normal. We have a Linksys wireless router and have the Cisco 2100 cable modem plugged into that.

Doing a traceroute showed <1ms to the router, and then >1000ms on the 2nd hop - the modem. So we got a new modem out (the Cisco 2100, used to have an old ntl 120) and the problem still happens. So you'd think it was the router, maybe a bad WAN port? So today, I got a new wireless router (again Linksys) and it's still doing this.

I'm just lost now. A new modem and a new router, and it's still doing it. As a VM tech advised, modem is straight into the PC now and I'm doing a continuous ping to google.co.uk to see if it goes slow.

So what if it doesnt go slow? How can two routers be faulty (when the first had been working for 2/3 years without issues)? Could it be an MTU setting? It had been at 1500 for the 2/3 years, tried putting it down with no difference.

Please any help

[Sephiroth]

Can we see the results of PATHPING www.bbc.co.UK please?

[psmith98752]

Thanks for replying, totally stuck with this one. The internet is going slow now.

First, heres was ping bbc.co.uk -t looks like:

C:\Users\Me>ping bbc.co.uk -t

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=1319ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1299ms TTL=118
Reply from 212.58.224.138: bytes=32 time=987ms TTL=118
Reply from 212.58.224.138: bytes=32 time=823ms TTL=118
Reply from 212.58.224.138: bytes=32 time=826ms TTL=118
Reply from 212.58.224.138: bytes=32 time=961ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1122ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1152ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1063ms TTL=118
Reply from 212.58.224.138: bytes=32 time=913ms TTL=118
Reply from 212.58.224.138: bytes=32 time=907ms TTL=118
Reply from 212.58.224.138: bytes=32 time=974ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1125ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1028ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1102ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1165ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1176ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1240ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1266ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1239ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1303ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1326ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1091ms TTL=118
Reply from 212.58.224.138: bytes=32 time=843ms TTL=118
Reply from 212.58.224.138: bytes=32 time=682ms TTL=118
Reply from 212.58.224.138: bytes=32 time=875ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1034ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1279ms TTL=118
Reply from 212.58.224.138: bytes=32 time=1443ms TTL=118

Here's a traceroute:

C:\Users\Me>tracert bbc.co.uk

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.2.1
2 1801 ms 1811 ms 1625 ms 10.232.208.1
3 2007 ms * 1775 ms renf-cam-1a-v124.network.virginmedia.net [80.4.6
4.17]
4 1344 ms 1468 ms 1614 ms renf-core-1a-ae2-0.network.virginmedia.net [195.
182.176.165]
5 1717 ms 1883 ms 1892 ms manc-bb-1a-as4-0.network.virginmedia.net [213.10
5.175.221]
6 2048 ms 2021 ms * glfd-bb-1b-ae1-0.network.virginmedia.net [213.10
5.175.146]
7 1876 ms 1961 ms 2094 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.
185.78]
8 1907 ms 1972 ms 2038 ms 212.58.239.249
9 1496 ms 1373 ms 1309 ms 212.58.238.133
10 1676 ms 1717 ms 1775 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Finally pathping (which took a good few minutes):

C:\Users\Me>pathping bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
0 MYPCNAME.cable.virginmedia.net [192.168.2.202]
1 192.168.2.1
2 10.232.208.1
3 renf-cam-1a-v124.network.virginmedia.net [80.4.64.17]
4 renf-core-1a-ae2-0.network.virginmedia.net [195.182.176.165]
5 manc-bb-1a-as4-0.network.virginmedia.net [213.105.175.221]
6 glfd-bb-1b-ae1-0.network.virginmedia.net [213.105.175.146]
7 redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
8 212.58.239.249
9 212.58.238.133
10 virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Marcus-PC.cable.virginmedia.net [1
92.168.2.202]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1
1/ 100 = 1% |
2 --- 100/ 100 =100% 99/ 100 = 99% 10.232.208.1
0/ 100 = 0% |
3 1484ms 3/ 100 = 3% 2/ 100 = 2% renf-cam-1a-v124.network.virginmed
ia.net [80.4.64.17]
0/ 100 = 0% |
4 1477ms 2/ 100 = 2% 1/ 100 = 1% renf-core-1a-ae2-0.network.virginm
edia.net [195.182.176.165]
0/ 100 = 0% |
5 1486ms 1/ 100 = 1% 0/ 100 = 0% manc-bb-1a-as4-0.network.virginmed
ia.net [213.105.175.221]
0/ 100 = 0% |
6 1485ms 1/ 100 = 1% 0/ 100 = 0% glfd-bb-1b-ae1-0.network.virginmed
ia.net [213.105.175.146]
0/ 100 = 0% |
7 1484ms 2/ 100 = 2% 1/ 100 = 1% redb-ic-1-as0-0.network.virginmedi
a.net [62.253.185.78]
0/ 100 = 0% |
8 --- 100/ 100 =100% 99/ 100 = 99% 212.58.239.249
0/ 100 = 0% |
9 1486ms 5/ 100 = 5% 4/ 100 = 4% 212.58.238.133
0/ 100 = 0% |
10 1483ms 1/ 100 = 1% 0/ 100 = 0% virtual-vip.thdo.bbc.co.uk [212.58
.224.138]

Trace complete.

I should note that during pathping doing it's thing, the internet went back to normal again. ie heres a new traceroute:

C:\Users\Me>tracert bbc.co.uk

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.2.1
2 11 ms 9 ms 10 ms 10.232.208.1
3 18 ms 30 ms 20 ms renf-cam-1a-v124.network.virginmedia.net [80.4.6
4.17]
4 12 ms 9 ms 9 ms renf-core-1a-ae2-0.network.virginmedia.net [195.
182.176.165]
5 11 ms 12 ms 39 ms manc-bb-1a-as4-0.network.virginmedia.net [213.10
5.175.221]
6 19 ms 22 ms 19 ms glfd-bb-1b-ae1-0.network.virginmedia.net [213.10
5.175.146]
7 29 ms 20 ms 22 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.
185.78]
8 45 ms 37 ms 47 ms 212.58.239.249
9 22 ms 24 ms 20 ms 212.58.238.133
10 39 ms 20 ms 21 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

[psmith98752]

I hate to bump when i'm asking for help but does anyone have any ideas?

Please also see http://www.dslreports.com/linequality/nil/2629828 which shows high pings from an external network to my IP address. Does this suggest the problem is a Virgin's end?

[Sephiroth]

Sorry not to join earlier. Been busy.

It would indeed suggest a problem at Virgin's end if we could rule out your router. I would have done this test when directly connected to the modem (or is that what you did - can't tell)? You were connected to the router for the pathping and it seems clear to me that between hops 2 & 3 is where the delay occurs. The 10.xx address represents the UBR being the private IP address assigned to you.

I suppose it's time to see your modem stats and event log.

[psmith98752]

Thanks for replying Fully appreciate you helping out in your spare time.

I've not yet had the problem when the modem has been connected directly to the computer. Maybe because it's hardly been connected directly because its so inconvenient but I guess I'll have to try. All those tests were through the router. What I can't understand is that we had this problem with the old router and the old modem. Same thing with the new router and new modem.

[Sephiroth]

I'm sure you've got upstream problems and should be reported to VM. The batch of T3s today support this as does the pathping.

I won't comment on pingtest because it tells us nothing about where delay is occurring and is frankly useless!

[Welshchris]

Originally Posted by Sephiroth

I'm sure you've got upstream problems and should be reported to VM. The batch of T3s today support this as does the pathping.

I won't comment on pingtest because it tells us nothing about where delay is occurring and is frankly useless!

there r nutorious problems in Swansea with the T3 errors on upstream from Motorolla BSRs. This is whats causing my intermittant Issues but all i get when asked when it will be sorted is Motorolla is still looking at the issue.

I can get sometimes as many as 80T3 erros register on my modem.

I know that this may not be the case here but what im stating is im sure its a problem on a lot of the network using Cisco and Motorolla and im also still adament they have routing issues that are intermittant.

[psmith98752]

Originally Posted by Sephiroth

I'm sure you've got upstream problems and should be reported to VM. The batch of T3s today support this as does the pathping.

Many thanks Seph. Although I'm a bit techie, I've only read a tiny bit on the net about T3 errors. If my SNR/power levels are fine, what could be causing this? What should I be telling Virgin? No offence but I always seem to get through to people who read off of screens trying to tell me to reboot the modem (which solves the problem for a few minutes).

Is there a specific department other than broadband technical support I should speak to? What should I say, ie what evidence can I show that its a problem at their end as they always do a test from their end and say its fine.

[Sephiroth]

Originally Posted by Welshchris

....I can get sometimes as many as 80T3 erros register on my modem.

I know that this may not be the case here but what im stating is im sure its a problem on a lot of the network using Cisco and Motorolla and im also still adament they have routing issues that are intermittant.

I didn't know there were systemic errors on the Cisco 10Ks. I thought it was confined to the BSRs.

What's the evidence? I forget what the Swansea CMTS scene is.

---------- Post added at 22:10 ---------- Previous post was at 22:06 ----------

Originally Posted by psmith98752

Many thanks Seph. Although I'm a bit techie, I've only read a tiny bit on the net about T3 errors. If my SNR/power levels are fine, what could be causing this? What should I be telling Virgin? ...

Is there a specific department other than broadband technical support I should speak to? What should I say, ie what evidence can I show that its a problem at their end as they always do a test from their end and say its fine.

Forget the ridiculous telephone support disaster. You should report this with your stats on the VM support forum. The 2nd line support people will take a look at the upstream because of the T3 errors. They would look at the SNR and stats from the UBR - something only they can see.

[psmith98752]

Originally Posted by Sephiroth

Forget the ridiculous telephone support disaster. You should report this with your stats on the VM support forum. The 2nd line support people will take a look at the upstream because of the T3 errors. They would look at the SNR and stats from the UBR - something only they can see.

Thanks, just checking, its here I post this: http://community.virginmedia.com/t5/...ble/bd-p/Fibre ?