Ridiculous ping yet down/up speeds are fine?

Associate
Joined
3 Oct 2014
Posts
581
Location
South West
Just ran a speedtest from my local server and I'm getting a ping of 90... It should be around 6-10. Same issue yesterday, and it's only been happening since then. I was up until late last night and at around midnight it finally passed, but upon arriving home from another 11 hour day to find it's occurring again is pretty irritating to say the least.

Any recommendations, bar calling up the ISP to complain, on what the actual issue is to give me some understanding?
 
Who's your ISP?

Try running a traceroute with the tracert command and see where the loops are with high ping. I had this the other week with VM and my connection to London was going via Germany!
 
Virgin Media.

Other bit of info which may help, I'm getting literally no packet loss at all... :s

There's no like spikes, it's literally sitting constantly above 100 now (on ts, UK server that is) and I'm the only person on the net in my house. My friend suggested it's most likely a line fault so get an engineer out - I'll be on the phone to them shortly to arrange that but yeah, just wanted potential known issues/greater understanding.

Cheers for now Finners :)
 
Finners, how do you find out where the connections are 'going through'? I'm not massively clued up on cmd inputs being honest - done a quick Google on how to use it at least.
 
Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=108ms TTL=54
Reply from 212.58.244.20: bytes=32 time=112ms TTL=54
Reply from 212.58.244.20: bytes=32 time=114ms TTL=54
Reply from 212.58.244.20: bytes=32 time=112ms TTL=54

Ping statistics for 212.58.244.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 114ms, Average = 111ms

----

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

1 * * * Request timed out.
2 104 ms 106 ms 107 ms aztw-core-2b-xe-714-0.network.virginmedia.net [62.252.231.205]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 112 ms 114 ms 111 ms 212.58.239.249
7 * * * Request timed out.
8 * * * Request timed out.
9 113 ms 113 ms 113 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 114 ms 114 ms 114 ms 132.185.255.149
11 114 ms 114 ms 114 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.
 
YES! Another person!

I called today and they have no knowledge, yet this says something different.

134598753.png


Please tell me your location? My Locale is Bristol, and experiencing ping issues, and intermittent packet loss. It went last night around ~9PM along with TV which went out for ~10 seconds whilst we were watching. For any doubters, my usual ping is around 10-20 with 0-1MS of jitter i.e fantastic.
 
Last edited:
Pingu, I have been on the phone twice, and I now have an engineer booked in. I imagine he'll fix at the exchange... hoping it's that due to it seeming to be the SW Region... if you're in Bristol then maybe local to here.

Booked for Monday 26th which is "earliest" he said... but better than nothing.
 
Factory default your hub, put it into bridge mode, plug one laptop in via a cable, wait for a DHCP lease to give you an IP. Try your tests again, post the results.

Also post traceroute results because I imagine you're being routed in a crazy path to get latency like that.
 
Finners, how do you find out where the connections are 'going through'? I'm not massively clued up on cmd inputs being honest - done a quick Google on how to use it at least.

Just run it through an IP checker website like https://www.iplocation.net/.

Problem for you is the loops you are getting timed out on are likely the ones that could be in europe.

This was my result from a few weeks ago, the telia.net is in europe. But my results today look like yours with a lot of timing out, although my connection is stable. If I put my conspiracy hat on it seems they might be blocking it somehow to hide that they are offloading their traffic onto other networks due to over subscription.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 8 ms 6 ms 8 ms cosh-core-2b-xe-012-0.network.virginmedia.net [8
6.6.35.113]
4 9 ms 9 ms 9 ms brnt-bb-1c-ae17-0.network.virginmedia.net [80.3.
160.250]
5 16 ms 15 ms 14 ms ae10-xcr1.lnd.cw.net [195.2.9.149]
6 16 ms 18 ms 16 ms ae2-xcr1.hex.cw.net [195.2.24.158]
7 127 ms 128 ms 131 ms ldn-b3-link.telia.net [62.115.41.109]
8 135 ms 137 ms 138 ms vultr-ic-312912-ldn-b3.c.telia.net [62.115.58.26
]
9 130 ms 131 ms 130 ms 104.238.175.55.vultr.com [104.238.175.55]
10 129 ms 149 ms 126 ms sherlock.mymumble.com [209.222.30.85]
 
Pingu, I have been on the phone twice, and I now have an engineer booked in. I imagine he'll fix at the exchange... hoping it's that due to it seeming to be the SW Region... if you're in Bristol then maybe local to here.

Booked for Monday 26th which is "earliest" he said... but better than nothing.

*Scoffs* I'm Bristol mate, thanks for some form of reassurance though - seems to be just Virgin Media that's having the issue which would seem to me there's an issue with the exchange as you said. Blah, sucks2beus when I'm in a CSGO team, trying to play regularly and move up the leagues -_- also that my family members can't even get onto PSN or Steam via laptop/ps. It's **** :(

Just run it through an IP checker website like https://www.iplocation.net/.

Problem for you is the loops you are getting timed out on are likely the ones that could be in europe.

This was my result from a few weeks ago, the telia.net is in europe. But my results today look like yours with a lot of timing out, although my connection is stable. If I put my conspiracy hat on it seems they might be blocking it somehow to hide that they are offloading their traffic onto other networks due to over subscription.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 8 ms 6 ms 8 ms cosh-core-2b-xe-012-0.network.virginmedia.net [8
6.6.35.113]
4 9 ms 9 ms 9 ms brnt-bb-1c-ae17-0.network.virginmedia.net [80.3.
160.250]
5 16 ms 15 ms 14 ms ae10-xcr1.lnd.cw.net [195.2.9.149]
6 16 ms 18 ms 16 ms ae2-xcr1.hex.cw.net [195.2.24.158]
7 127 ms 128 ms 131 ms ldn-b3-link.telia.net [62.115.41.109]
8 135 ms 137 ms 138 ms vultr-ic-312912-ldn-b3.c.telia.net [62.115.58.26
]
9 130 ms 131 ms 130 ms 104.238.175.55.vultr.com [104.238.175.55]
10 129 ms 149 ms 126 ms sherlock.mymumble.com [209.222.30.85]

Thanks for the (sort of) reassurance on a potential issue - it does make sense that they'd get an oversubscription that they can't fulfil seeing as the internet architecture we have laid in the UK is bloody dreadful compared to many other countries, especially considering high-speed was supposed to be all over consistent like 3 years ago!

Also, here's a screenshot [link] using my ip on the link you sent. https://gyazo.com/77084dd98fb35840a335403484a0f353 I'd upload a direct screen but for some reason I can't get 'em to work direct from gyazo and I'm too tired to go through uploading somewhere haha.
 
Last edited:
*Scoffs* I'm Bristol mate, thanks for some form of reassurance though - seems to be just Virgin Media that's having the issue which would seem to me there's an issue with the exchange as you said. Blah, sucks2beus when I'm in a CSGO team, trying to play regularly and move up the leagues -_- also that my family members can't even get onto PSN or Steam via laptop/ps. It's **** :(

I now have more information for you, courtesy of VM forums for area 07 which I think you're in (same as me).

"Just spoke to a lovely chap on the support line. He confirmed they were doing capacity upgrades in the area and have temporarily shunted all customers onto one line. He said it should last a maximum of 48 hours between 21:00 and 23:30 being the worst due to usage. After that, it should be fine."


Hope that helps buddy.
 
I now have more information for you, courtesy of VM forums for area 07 which I think you're in (same as me).

"Just spoke to a lovely chap on the support line. He confirmed they were doing capacity upgrades in the area and have temporarily shunted all customers onto one line. He said it should last a maximum of 48 hours between 21:00 and 23:30 being the worst due to usage. After that, it should be fine."


Hope that helps buddy.

Correct, same area code :) Massive help thanks mate. Would explain why my ping was fine from midnight onwards until I got off at about 2am last night. Seems there are a lot of night owls on VM ha! Keep me posted on your situation fella, as I say this has effectively been over 2 days already so as of now I'm expecting it to be bog for up to Thursday but no later than!
 
Just be aware that Finners is showing totally different potential causes of latency to you. You've got 100ms+ of delay at the second hop within Virgin's network. Finners' traceroute is showing a potentially congested link between C&W and Telia.
 
Thanks for the heads up Caged. I do believe as rexehuk is in the same area as me experiencing the issue too it seems his explanation is logical, given I've just jumped on an ESEA game and got the highest rws on the server :p comeback was real, 9-6 down on Cache going into t side, won 16-11 haha
 
Just lucky you're not off work at the moment! Check this bad boy.

134630172.png

4842330705.png


60Mbit line...

Flamin' heck that's awful :( just got home, it's still dreadful. Feel like I'm in a horror movie, "I just can't wait until all this is over!" :rolleyes:

Edit: Wait, why were you pinging from a server in the Netherlands? lol

Again: Wait.. Ignore that, just seen it was 2 separate tests. Fudge.
 
Flamin' heck that's awful :( just got home, it's still dreadful. Feel like I'm in a horror movie, "I just can't wait until all this is over!" :rolleyes:

Edit: Wait, why were you pinging from a server in the Netherlands? lol

Again: Wait.. Ignore that, just seen it was 2 separate tests. Fudge.

Surprised yours is not the same? It is worse than last night, by a factor of around 6X. However this time there is also now packet loss, and speed has been affected massively.

Even loading websites/streaming is near on impossible.

4843653739.png

134652765.png
 
Last edited:
Back
Top Bottom