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

Latency issues

Hi,

I’m struggling with major lag which has now made gaming virtually impossible. Restarting the Hub doesn’t work at all. How can I get this issue rectified?

Any help would be greatly appreciated

Thanks

 

0 Kudos
Reply
Highlighted
  • 18
  • 1
  • 2
On our wavelength
280 Views
Message 2 of 13
Flag for a moderator

Re: Latency issues

http://www.pingplotter.com/

download that and have a look see - who ever helps you out here is going to want evidence of your latency, and where it occurs from source to destination.

you might wanna also post your VM hub 'current stats"

0 Kudos
Reply
Highlighted
  • 5
  • 0
  • 0
Joining in
274 Views
Message 3 of 13
Flag for a moderator

Re: Latency issues

0 Kudos
Reply
Highlighted
  • 213
  • 6
  • 34
Superfast
236 Views
Message 4 of 13
Flag for a moderator

Re: Latency issues

86.85-254-62.static.virginmediabusiness.co.uk

wolv-core-2a-xe-7117-0.network.virginmedia.net


are where my latency occurs.

 

 

 

Unacceptable to a game hosted in the Netherlands.

 

 

And no it's not my PC, this pc was recently kitted out with a brand new motherboard (which means brand new ethernet controller) and more components as well as a brand new cat 7 cable.

0 Kudos
Reply
Highlighted
  • 13.61K
  • 553
  • 1.27K
Alessandro Volta
232 Views
Message 5 of 13
Flag for a moderator

Re: Latency issues

You could post the full tracert

also do a ping -n 200 to VM gateway or 194.168.4.100

---------------------------------------------------------------
BQM, Test for outgoing ports and L2TP VPN test
0 Kudos
Reply
Highlighted
  • 5
  • 0
  • 0
Joining in
193 Views
Message 6 of 13
Flag for a moderator

Re: Latency issues

https://www.thinkbroadband.com/broadband/monitoring/quality/share/c0c25266d49f6047fd6fab41e6149e7a4d... 

Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=88ms TTL=61
Reply from 194.168.4.100: bytes=32 time=242ms TTL=61
Reply from 194.168.4.100: bytes=32 time=75ms TTL=61
Reply from 194.168.4.100: bytes=32 time=67ms TTL=61

Ping statistics for 194.168.4.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 242ms, Average = 118ms

0 Kudos
Reply
Highlighted
  • 213
  • 6
  • 34
Superfast
182 Views
Message 7 of 13
Flag for a moderator

Re: Latency issues

Virgin doesn't care as long as our bills are paid each month.

Hundred's are complaining about latency and nothing's getting done.


Soon as Openreach allows orders again I'm getting an FTTC connection so I can game.
0 Kudos
Reply
Highlighted
  • 13.61K
  • 553
  • 1.27K
Alessandro Volta
172 Views
Message 8 of 13
Flag for a moderator

Re: Latency issues

looks like a port in the VM network hit high utilisation

---------------------------------------------------------------
BQM, Test for outgoing ports and L2TP VPN test
0 Kudos
Reply
Highlighted
  • 5
  • 0
  • 0
Joining in
155 Views
Message 9 of 13
Flag for a moderator

Re: Latency issues

What does that mean? VM haven't got the capacity?

0 Kudos
Reply
Highlighted
  • 213
  • 6
  • 34
Superfast
150 Views
Message 10 of 13
Flag for a moderator

Re: Latency issues

That's exactly what he means.


Virgin's current capacity cannot cope so service is degraded.


0 Kudos
Reply