Menu
Reply
Highlighted
  • 5
  • 0
  • 0
Joining in
260 Views
Message 1 of 5
Flag for a moderator

Lag spikes and packet loss

Hi all,

I am suffering from lag spikes every now and then, for example - I used the SuperHub 3.0 Ping to find out what's going on and the example is copied below.

I did this test on a Desktop plugged in through an Ethernet - I've the line tests offered on both the Virgin media website and on the router and has found nothing wrong.

Can someone help?

 

PING www.google.com (216.58.204.36): 64 data bytes
72 bytes from 216.58.204.36: seq=0 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=1 ttl=55 time=140.000 ms
72 bytes from 216.58.204.36: seq=2 ttl=55 time=240.000 ms
72 bytes from 216.58.204.36: seq=3 ttl=55 time=50.000 ms
72 bytes from 216.58.204.36: seq=4 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=5 ttl=55 time=10.000 ms
72 bytes from 216.58.204.36: seq=6 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=7 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=8 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=9 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=10 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=11 ttl=55 time=10.000 ms
72 bytes from 216.58.204.36: seq=12 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=13 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=14 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=15 ttl=55 time=10.000 ms
72 bytes from 216.58.204.36: seq=16 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=17 ttl=55 time=20.000 ms
72 bytes from 216.58.204.36: seq=18 ttl=55 time=10.000 ms
72 bytes from 216.58.204.36: seq=19 ttl=55 time=30.000 ms
72 bytes from 216.58.204.36: seq=20 ttl=55 time=10.000 ms
72 bytes from 216.58.204.36: seq=21 ttl=55 time=20.000 ms
--- www.google.com ping statistics ---
25 packets transmitted, 22 packets received, 12% packet loss
round-trip min/avg/max = 10.000/35.000/240.000 ms

0 Kudos
Reply
Highlighted
  • 12.44K
  • 859
  • 3.71K
Very Insightful Person
Very Insightful Person
240 Views
Message 2 of 5
Flag for a moderator

Re: Lag spikes and packet loss

Dont. Use a command line.

And try BBC.co.uk, post that trace and ping results.

 

As a Very Insightful Person, I'm here to share my knowledge. I don't work for Virgin Media.

Click to learn more about VIP

Use Kudos to say thanks

Mark as Helpful Answer if I've helped

0 Kudos
Reply
Highlighted
  • 3K
  • 174
  • 394
Forum Team
Forum Team
205 Views
Message 3 of 5
Flag for a moderator

Re: Lag spikes and packet loss

Hey Jamzyluu

Just a quick message to see if you have tried a trace route with the BBC like @Kippies asked?

Gareth_L

0 Kudos
Reply
Highlighted
  • 5
  • 0
  • 0
Joining in
149 Views
Message 4 of 5
Flag for a moderator

Re: Lag spikes and packet loss

Apologies for late reply -

I did the trace route -

C:\Users\JAMZY>ping google.com -t

Pinging google.com [216.58.213.14] with 32 bytes of data:
Reply from 216.58.213.14: bytes=32 time=25ms TTL=55
Request timed out.
Reply from 216.58.213.14: bytes=32 time=26ms TTL=55
Reply from 216.58.213.14: bytes=32 time=151ms TTL=55
Reply from 216.58.213.14: bytes=32 time=224ms TTL=55
Reply from 216.58.213.14: bytes=32 time=54ms TTL=55
Reply from 216.58.213.14: bytes=32 time=47ms TTL=55
Reply from 216.58.213.14: bytes=32 time=30ms TTL=55
Reply from 216.58.213.14: bytes=32 time=105ms TTL=55
0 Kudos
Reply
Highlighted
  • 5
  • 0
  • 0
Joining in
149 Views
Message 5 of 5
Flag for a moderator

Re: Lag spikes and packet loss

Hi Kippies,

Apologies for late reply -

Here is the ping results

C:\Users\JAMZY>ping google.com -t

Pinging google.com [216.58.213.14] with 32 bytes of data:
Reply from 216.58.213.14: bytes=32 time=25ms TTL=55
Request timed out.
Reply from 216.58.213.14: bytes=32 time=26ms TTL=55
Reply from 216.58.213.14: bytes=32 time=151ms TTL=55
Reply from 216.58.213.14: bytes=32 time=224ms TTL=55
Reply from 216.58.213.14: bytes=32 time=54ms TTL=55
Reply from 216.58.213.14: bytes=32 time=47ms TTL=55
Reply from 216.58.213.14: bytes=32 time=30ms TTL=55
Reply from 216.58.213.14: bytes=32 time=105ms TTL=55
0 Kudos
Reply