cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
h3x1e
Expert
1,307 Views
Message 21 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

Update:

After the Openreach Qube Engineer visit on Friday, I hadn't heard from BT so I chased them up this morning.

The case has now been escalated and an Engineer has been sent out to check the Frames Unit, as this is where the issue is probably stemming from.

Will keep you posted.

 

0 Ratings
Reply
h3x1e
Expert
1,289 Views
Message 22 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

So Live Chat are absolutely useless, they started putting Landline connection Faults though, they've closed my broadband fault, saying there isn't a problem when the Openreach Engineer clearly stated there was.

There has not been Openreach Fibre Engineer visit booked as stated by the first OR Engineer. BT just seem to be shrugging this case off like the many others?

I'm going to keep this thread updated daily now with the same ping issues that everyone else is experiencing.

@StephanieG 

h3x1e
Expert
1,282 Views
Message 23 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution
PS C:\WINDOWS\system32> ping -4 google.co.uk -t

Pinging google.co.uk [216.58.204.67] with 32 bytes of data:
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=66ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=66ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=66ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=68ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=29ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=66ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=68ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=67ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=21ms TTL=54
Reply from 216.58.204.67: bytes=32 time=20ms TTL=54

Ping statistics for 216.58.204.67:
    Packets: Sent = 82, Received = 82, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 68ms, Average = 29ms
0 Ratings
Reply
lolowalsh
Contributor
1,273 Views
Message 24 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

Try connection to BT Wi-Fi with fone, I got no ping spikes at all from it yesterday.

0 Ratings
Reply
h3x1e
Expert
1,268 Views
Message 25 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

Doesn't work your issue is different.

0 Ratings
Reply
h3x1e
Expert
1,254 Views
Message 26 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

ping -4 google.co.uk
PING google.co.uk (216.58.210.35) 56(84) bytes of data.
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=1 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=2 ttl=54 time=33.6 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=3 ttl=54 time=20.0 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=4 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=5 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=6 ttl=54 time=26.2 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=7 ttl=54 time=18.9 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=8 ttl=54 time=27.8 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=9 ttl=54 time=19.1 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=10 ttl=54 time=18.9 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=11 ttl=54 time=18.9 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=12 ttl=54 time=19.1 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=13 ttl=54 time=37.2 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=14 ttl=54 time=21.8 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=15 ttl=54 time=33.3 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=16 ttl=54 time=18.4 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=17 ttl=54 time=19.0 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=18 ttl=54 time=18.9 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=19 ttl=54 time=18.4 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=20 ttl=54 time=19.0 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=21 ttl=54 time=33.3 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=22 ttl=54 time=66.4 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=23 ttl=54 time=54.3 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=24 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=25 ttl=54 time=28.6 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=26 ttl=54 time=50.6 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=27 ttl=54 time=22.8 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=28 ttl=54 time=36.0 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=29 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=30 ttl=54 time=19.1 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=31 ttl=54 time=20.2 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=32 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=33 ttl=54 time=18.8 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=34 ttl=54 time=19.1 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=35 ttl=54 time=18.6 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=36 ttl=54 time=18.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=37 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=38 ttl=54 time=33.9 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=39 ttl=54 time=20.2 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=40 ttl=54 time=19.8 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=41 ttl=54 time=26.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=42 ttl=54 time=19.1 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=43 ttl=54 time=18.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=44 ttl=54 time=18.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=45 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=46 ttl=54 time=20.8 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=47 ttl=54 time=26.2 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=48 ttl=54 time=69.2 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=49 ttl=54 time=19.1 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=50 ttl=54 time=18.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=51 ttl=54 time=18.7 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=52 ttl=54 time=24.6 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=53 ttl=54 time=18.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=54 ttl=54 time=21.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=55 ttl=54 time=18.6 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=56 ttl=54 time=18.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=57 ttl=54 time=18.6 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=58 ttl=54 time=42.3 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=59 ttl=54 time=28.9 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=60 ttl=54 time=42.6 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=61 ttl=54 time=19.2 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=62 ttl=54 time=30.9 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=63 ttl=54 time=26.3 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=64 ttl=54 time=18.5 ms
64 bytes from lhr25s11-in-f35.1e100.net (216.58.210.35): icmp_seq=65 ttl=54 time=19.1 ms
^C
--- google.co.uk ping statistics ---
65 packets transmitted, 65 received, 0% packet loss, time 64067ms
rtt min/avg/max/mdev = 18.458/24.991/69.236/11.074 ms

0 Ratings
Reply
h3x1e
Expert
1,246 Views
Message 27 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

ping -4 google.co.uk
PING google.co.uk (172.217.169.35) 56(84) bytes of data.
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=1 ttl=54 time=45.6 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=2 ttl=54 time=21.7 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=3 ttl=54 time=21.9 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=4 ttl=54 time=22.1 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=5 ttl=54 time=22.0 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=6 ttl=54 time=55.0 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=7 ttl=54 time=21.8 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=8 ttl=54 time=21.6 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=9 ttl=54 time=21.8 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=10 ttl=54 time=22.0 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=11 ttl=54 time=54.3 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=12 ttl=54 time=40.8 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=13 ttl=54 time=22.4 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=14 ttl=54 time=21.6 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=15 ttl=54 time=22.1 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=16 ttl=54 time=24.4 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=17 ttl=54 time=22.2 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=18 ttl=54 time=21.7 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=19 ttl=54 time=54.5 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=20 ttl=54 time=53.8 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=21 ttl=54 time=21.9 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=22 ttl=54 time=21.6 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=23 ttl=54 time=21.8 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=24 ttl=54 time=49.4 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=25 ttl=54 time=53.7 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=26 ttl=54 time=21.9 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=27 ttl=54 time=22.0 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=28 ttl=54 time=21.9 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=29 ttl=54 time=56.0 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=30 ttl=54 time=55.3 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=31 ttl=54 time=21.7 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=32 ttl=54 time=22.1 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=33 ttl=54 time=21.7 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=34 ttl=54 time=21.9 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=35 ttl=54 time=55.0 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=36 ttl=54 time=22.0 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=37 ttl=54 time=22.2 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=38 ttl=54 time=21.9 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=39 ttl=54 time=55.8 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=40 ttl=54 time=54.5 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=41 ttl=54 time=22.1 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=42 ttl=54 time=21.8 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=43 ttl=54 time=22.0 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=44 ttl=54 time=22.3 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=45 ttl=54 time=21.8 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=46 ttl=54 time=22.1 ms
64 bytes from lhr48s08-in-f3.1e100.net (172.217.169.35): icmp_seq=47 ttl=54 time=21.8 ms
^C
--- google.co.uk ping statistics ---
47 packets transmitted, 47 received, 0% packet loss, time 46041ms
rtt min/avg/max/mdev = 21.656/30.505/56.065/13.890 ms

Activity, Watching Amazon Prime Video, as you can see ping spikes during this.

Max Network usage from my PC, I am the only one on the network right now.

This is about 6 Mbps of my 32Mbps sync speed / 34Mbps actual throughput speed.

Annotation 2019-07-04 135703.jpg

0 Ratings
Reply
h3x1e
Expert
1,229 Views
Message 28 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

h3x1e@Kings-WS:~$ ping -4 google.co.uk
PING google.co.uk (172.217.169.3) 56(84) bytes of data.
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=1 ttl=54 time=21.7 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=2 ttl=54 time=40.1 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=3 ttl=54 time=21.7 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=4 ttl=54 time=70.8 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=5 ttl=54 time=21.5 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=6 ttl=54 time=71.1 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=7 ttl=54 time=22.0 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=8 ttl=54 time=70.2 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=9 ttl=54 time=21.9 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=10 ttl=54 time=70.2 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=11 ttl=54 time=21.7 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=12 ttl=54 time=70.6 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=13 ttl=54 time=21.7 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=14 ttl=54 time=71.2 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=15 ttl=54 time=21.9 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=16 ttl=54 time=71.0 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=17 ttl=54 time=21.8 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=18 ttl=54 time=71.9 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=19 ttl=54 time=21.9 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=20 ttl=54 time=70.3 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=21 ttl=54 time=21.7 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=22 ttl=54 time=71.3 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=23 ttl=54 time=21.8 ms
64 bytes from lhr25s26-in-f3.1e100.net (172.217.169.3): icmp_seq=24 ttl=54 time=70.8 ms
^C
--- google.co.uk ping statistics ---
24 packets transmitted, 24 received, 0% packet loss, time 23022ms
rtt min/avg/max/mdev = 21.534/45.077/71.922/24.033 ms

0 Ratings
Reply
h3x1e
Expert
1,193 Views
Message 29 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

Some PingPlotter action for you today. Take note of Hops 3/4/5/6 ping spikes within BT's network.

Annotation 2019-07-06 193752.jpg

0 Ratings
Reply
h3x1e
Expert
1,174 Views
Message 30 of 295

Re: Latency Variation (Ping Spikes) during online gaming.

Go to solution

Today we have a PingLogger graph showing a ping to an Overwatch server with two different versions of the same twitch stream.

One Low Latency (2 seconds to broadcaster) the other with Normal Latency (7 seconds to broadcaster)

Low Latency Graph is on the left and as you can see the Normal Latency stream causes so much more issues with ping for some reason.

https://gyazo.com/fa7614937ecddde5a6c5cfcf665366d6

 

Black line = Low Latency Stream

Red line = Normal Latency

 

0 Ratings
Reply