Virgin Customers: What is your Ping?

GaryH-21 · 12 Jun 2011 at 20:15

I'm having some real bother here with virgin...

On a 10Mb line.... ping over 3000?! What the hell!!!!

Is anyone else experiencing similar?

kmufc77 · 12 Jun 2011 at 20:17

Not sure why im using a Midlands server lol,should be Milton Keynes

OP: Maybe there are issues in your area which that ping would maybe suggest,be patient and try again in a few hrs assuming this problem has only just started?

Phase · 12 Jun 2011 at 20:17

Same server DL is rubbish due to the Wifi to the laptop

Server thats best for me

wkingsnorth · 12 Jun 2011 at 20:21

I'd tell you but I can't connect to the damn router :/

Judgeneo · 12 Jun 2011 at 20:22

OP, repeat the test when connected to the virgin website

_Ad_ · 12 Jun 2011 at 20:23

19ms ping here.
On a 30meg connection, getting 30.71 download and around 3mb upload.

Subliminal Aura · 12 Jun 2011 at 20:29

Stop your torrents and retest.

I've seen 15 second pings on VM :/

bonehead666 · 12 Jun 2011 at 20:30

GaryH-21 · 12 Jun 2011 at 20:36

I've been having this problem for ages now.

I checked out the traffic management rules, and from what I can understand, I need to download 750MB to get a 5 hour speed reduction, but none of us have downloaded anywhere near that, and the reduction is 75% - last time I checked, 75% reduction of 10Mb isn't 0.5Mb

)

Judgeneo · 12 Jun 2011 at 20:38

Yeah my problems are very similar, I'm on the 20mb package.

Right now it won't even complete a speed test.

BloodyL · 12 Jun 2011 at 20:44

Haven't posted in a speedtest thread in ages. oooooh.

GaryH-21 · 12 Jun 2011 at 21:06

Judgeneo said:
OP, repeat the test when connected to the virgin website

You mean browse the VM site and do a speedtest? Didn't think it was possible, but it's worse!

Subliminal Aura said:
Stop your torrents and retest.

I've seen 15 second pings on VM :/

No downloads running what so ever. Just browsing here and VM right now - that's all!

Mel_P · 12 Jun 2011 at 21:10

Maidstone - 10ms to Sittingbourne on "Speedtest".

Mel

Judgeneo · 12 Jun 2011 at 21:12

Hmmn, when I did a speedtest the other day, being connected to the virgin site gave much better results. Must have just been a fluke.

Phone them up and complain, I was given £25 as a gesture or 'goodwill' last week. Apparently they have problems with their lines in my area.
Will be leaving next month when there is no cancellation fee anyway

Subliminal Aura · 12 Jun 2011 at 21:17

GaryH-21 said:
No downloads running what so ever. Just browsing here and VM right now - that's all!

Test for packet loss. winmtr / mtr or plain old ping off the commandline.

You could well have problems in your area or poor modem signal levels

ecksmen · 12 Jun 2011 at 21:45

50Mbps Virgin Media. Not the greatest results, but there's always traffic going through it and I'm on wireless.

Ping is as you'd expect for a wireless connection, good but not stable.

Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:
Reply from 84.234.17.86: bytes=32 time=23ms TTL=117
Reply from 84.234.17.86: bytes=32 time=22ms TTL=117
Reply from 84.234.17.86: bytes=32 time=39ms TTL=117
Reply from 84.234.17.86: bytes=32 time=23ms TTL=117
Reply from 84.234.17.86: bytes=32 time=47ms TTL=117
Reply from 84.234.17.86: bytes=32 time=19ms TTL=117
Reply from 84.234.17.86: bytes=32 time=42ms TTL=117
Reply from 84.234.17.86: bytes=32 time=25ms TTL=117
Reply from 84.234.17.86: bytes=32 time=20ms TTL=117
Reply from 84.234.17.86: bytes=32 time=62ms TTL=117
Reply from 84.234.17.86: bytes=32 time=85ms TTL=117
Reply from 84.234.17.86: bytes=32 time=108ms TTL=117
Reply from 84.234.17.86: bytes=32 time=107ms TTL=117
Reply from 84.234.17.86: bytes=32 time=32ms TTL=117
Reply from 84.234.17.86: bytes=32 time=24ms TTL=117
Reply from 84.234.17.86: bytes=32 time=24ms TTL=117
Reply from 84.234.17.86: bytes=32 time=40ms TTL=117
Reply from 84.234.17.86: bytes=32 time=27ms TTL=117

Edit

Wifi is crap for stable connection (255.1 is my router).

Pinging 192.168.255.1 with 32 bytes of data:
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time=4ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time=1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time=81ms TTL=64
Reply from 192.168.255.1: bytes=32 time=1ms TTL=64
Reply from 192.168.255.1: bytes=32 time=21ms TTL=64
Reply from 192.168.255.1: bytes=32 time=45ms TTL=64
Reply from 192.168.255.1: bytes=32 time=69ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time=1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64

And a wired counter part of 50 "pings".

Ping statistics for 192.168.255.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

GaryH-21 · 12 Jun 2011 at 21:59

C:\Users\Gary>ping -t 208.67.222.222

Pinging 208.67.222.222 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 208.67.222.222: bytes=32 time=3847ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 208.67.222.222: bytes=32 time=2689ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1737ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1291ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1690ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1916ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1165ms TTL=52
Reply from 208.67.222.222: bytes=32 time=705ms TTL=52
Reply from 208.67.222.222: bytes=32 time=408ms TTL=52
Reply from 208.67.222.222: bytes=32 time=27ms TTL=52
Reply from 208.67.222.222: bytes=32 time=106ms TTL=52
Reply from 208.67.222.222: bytes=32 time=129ms TTL=52
Reply from 208.67.222.222: bytes=32 time=191ms TTL=52
Reply from 208.67.222.222: bytes=32 time=419ms TTL=52
Reply from 208.67.222.222: bytes=32 time=244ms TTL=52
Reply from 208.67.222.222: bytes=32 time=472ms TTL=52
Reply from 208.67.222.222: bytes=32 time=219ms TTL=52
Reply from 208.67.222.222: bytes=32 time=169ms TTL=52
Reply from 208.67.222.222: bytes=32 time=91ms TTL=52
Reply from 208.67.222.222: bytes=32 time=22ms TTL=52

Ping statistics for 208.67.222.222:
Packets: Sent = 28, Received = 20, Lost = 8 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 3847ms, Average = 876ms

---------------------

Pinging the router gives me 0 packet loss.
Tried both wired and wireless

Sent them a message... hopefully they find a problem that's easy to fix...

Judgeneo · 12 Jun 2011 at 22:07

Open up command prompt and try pinging google.com

I just tried and got 50% packet loss. My ping isn't anywhere near as bad as yours though

ecksmen · 12 Jun 2011 at 22:28

GaryH-21 said:
C:\Users\Gary>ping -t 208.67.222.222

Pinging 208.67.222.222 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 208.67.222.222: bytes=32 time=3847ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 208.67.222.222: bytes=32 time=2689ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1737ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1291ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1690ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1916ms TTL=52
Reply from 208.67.222.222: bytes=32 time=1165ms TTL=52
Reply from 208.67.222.222: bytes=32 time=705ms TTL=52
Reply from 208.67.222.222: bytes=32 time=408ms TTL=52
Reply from 208.67.222.222: bytes=32 time=27ms TTL=52
Reply from 208.67.222.222: bytes=32 time=106ms TTL=52
Reply from 208.67.222.222: bytes=32 time=129ms TTL=52
Reply from 208.67.222.222: bytes=32 time=191ms TTL=52
Reply from 208.67.222.222: bytes=32 time=419ms TTL=52
Reply from 208.67.222.222: bytes=32 time=244ms TTL=52
Reply from 208.67.222.222: bytes=32 time=472ms TTL=52
Reply from 208.67.222.222: bytes=32 time=219ms TTL=52
Reply from 208.67.222.222: bytes=32 time=169ms TTL=52
Reply from 208.67.222.222: bytes=32 time=91ms TTL=52
Reply from 208.67.222.222: bytes=32 time=22ms TTL=52

Ping statistics for 208.67.222.222:
Packets: Sent = 28, Received = 20, Lost = 8 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 3847ms, Average = 876ms

---------------------

Pinging the router gives me 0 packet loss.
Tried both wired and wireless

Sent them a message... hopefully they find a problem that's easy to fix...

Try

pathping 208.67.222.222

for info, to opendns I get

Pinging 208.67.222.222 with 32 bytes of data:
Reply from 208.67.222.222: bytes=32 time=18ms TTL=55
Reply from 208.67.222.222: bytes=32 time=21ms TTL=55
Reply from 208.67.222.222: bytes=32 time=21ms TTL=55
Reply from 208.67.222.222: bytes=32 time=20ms TTL=55
Reply from 208.67.222.222: bytes=32 time=18ms TTL=55
Reply from 208.67.222.222: bytes=32 time=19ms TTL=55
Reply from 208.67.222.222: bytes=32 time=19ms TTL=55
Reply from 208.67.222.222: bytes=32 time=23ms TTL=55
Reply from 208.67.222.222: bytes=32 time=21ms TTL=55

tracerts can also show possible routing issues.

ecksmen · 12 Jun 2011 at 22:33

http://www.pingplotter.com/ < may be of some good use. Can run it for hours to give to VM to prove where delays may be.