Forum Discussion

Wight87's avatar
Wight87
Joining in
17 days ago

Jitter within VM tolerances?

Hello all,

Been with VM since september, i've noticed jitter on my ping tests. I know that the virgin gets more jitter then an open reach line, but im not sure by how much?

Below is a ping test that i did, hard wired to the VM router to google.co.uk

Is this within Tolerance for gaming? How much jitter would fellow games allow before getting VM involved?

:\Users\mickw>ping google.co.uk -n 100

Pinging google.co.uk [172.217.16.227] with 32 bytes of data:
Reply from 172.217.16.227: bytes=32 time=19ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=15ms TTL=116
Reply from 172.217.16.227: bytes=32 time=15ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=35ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=22ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=20ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=24ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=20ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=19ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=20ms TTL=116
Reply from 172.217.16.227: bytes=32 time=15ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=21ms TTL=116
Reply from 172.217.16.227: bytes=32 time=20ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=20ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=19ms TTL=116
Reply from 172.217.16.227: bytes=32 time=24ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=19ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=28ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=15ms TTL=116
Reply from 172.217.16.227: bytes=32 time=26ms TTL=116
Reply from 172.217.16.227: bytes=32 time=25ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=19ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=17ms TTL=116
Reply from 172.217.16.227: bytes=32 time=19ms TTL=116
Reply from 172.217.16.227: bytes=32 time=19ms TTL=116
Reply from 172.217.16.227: bytes=32 time=16ms TTL=116
Reply from 172.217.16.227: bytes=32 time=18ms TTL=116
Reply from 172.217.16.227: bytes=32 time=15ms TTL=116

Ping statistics for 172.217.16.227:
Packets: Sent = 89, Received = 89, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 35ms, Average = 17ms

 

  • unisoft's avatar
    unisoft
    17 days ago

    Figures as expected on coax HFC network.....nothing to see, move on......

  • Wight87's avatar
    Wight87
    Joining in
    17 days ago

    Update:#

    I did a speed /jitter test from VM website and my results are below, the 1.44ms in jitter is not what im seeing in my ping test within CMD. unless my ping test isnt reliable? Do VM use some sort of traffic management so that gaming and VOIP is prioritised? Sorry for the further questions.

    Latency:15.6ms

    Jitter 1.44ms

    Download 276mbps

    Upload 17.8mbps

     

     

    • unisoft's avatar
      unisoft
      Knows their stuff
      17 days ago

      Figures as expected on coax HFC network.....nothing to see, move on......

  • Client62's avatar
    Client62
    Alessandro Volta
    16 days ago

    Focus on why your upload is running slow, 25 Mb/s is expected for M250.

    Find out where the speed is being lost ..

    https://www.samknows.com/realspeed/
    This is also available as iPhone & Android apps called : "Samknows Realspeed"

    Once the test begins click on: Run full test to include: Latency, Jitter, Packet loss & Upload speed.
    Share a screen shot of the Full Test result.