cancel
Showing results for 
Search instead for 
Did you mean: 
lolowalsh
Contributor
403 Views
Message 51 of 276

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

@h3x1e  I got a text from BT that my connection would be stable and it actually it is for the first time, I can play YouTube and my ping spikes to 20 ms instead of 300 now so finger crossed. 

 

It's too early to say it's fixed and I will continue to monitor it but today been the best compared the past few weeks, fifa is actually playable now when I stream something on YouTube.

h3x1e
Aspiring Expert
390 Views
Message 52 of 276

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

Let me know, because mine is still all over the place.

0 Ratings
Reply
h3x1e
Aspiring Expert
385 Views
Message 53 of 276

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

h3x1e@Kings-WS:~$ ping -4 google.co.uk
PING google.co.uk (216.58.204.35) 56(84) bytes of data.
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=1 ttl=54 time=21.6 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=2 ttl=54 time=21.6 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=3 ttl=54 time=21.9 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=4 ttl=54 time=21.7 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=5 ttl=54 time=21.6 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=6 ttl=54 time=22.4 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=7 ttl=54 time=22.2 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=8 ttl=54 time=21.9 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=9 ttl=54 time=21.6 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=10 ttl=54 time=22.1 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=11 ttl=54 time=22.0 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=12 ttl=54 time=22.5 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=13 ttl=54 time=26.2 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=14 ttl=54 time=21.6 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=15 ttl=54 time=21.9 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=16 ttl=54 time=22.0 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=17 ttl=54 time=21.7 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=18 ttl=54 time=22.2 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=19 ttl=54 time=25.9 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=20 ttl=54 time=63.8 ms - SPIKE
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=21 ttl=54 time=53.3 ms -SPIKE
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=22 ttl=54 time=117 ms - SPIKE
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=23 ttl=54 time=60.9 ms -SPIKE
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=24 ttl=54 time=34.6 ms - SPIKE
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=25 ttl=54 time=22.0 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=26 ttl=54 time=21.8 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=27 ttl=54 time=21.7 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=28 ttl=54 time=30.2 ms - SPIKE
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=29 ttl=54 time=47.1 ms - SPIKE
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=30 ttl=54 time=25.4 ms
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=31 ttl=54 time=32.5 ms - SPIKE
64 bytes from lhr25s12-in-f3.1e100.net (216.58.204.35): icmp_seq=32 ttl=54 time=112 ms - SPIKE
^C
--- google.co.uk ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31032ms
rtt min/avg/max/mdev = 21.618/33.420/117.617/23.981 ms

 

While watching a Youtube Video.

0 Ratings
Reply
lolowalsh
Contributor
377 Views
Message 54 of 276

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

take that back, back to absolute **bleep** this morning, 3 ping spikes at 10, 11, 12 pm up to 355 ms.

h3x1e
Aspiring Expert
367 Views
Message 55 of 276

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

Tonight's results:

Better than usual but still seeing spikes of 10ms ish in places. 

h3x1e@Kings-WS:~$ ping -4 google.co.uk
PING google.co.uk (216.58.206.99) 56(84) bytes of data.
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=1 ttl=54 time=20.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=2 ttl=54 time=18.4 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=3 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=4 ttl=54 time=27.9 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=5 ttl=54 time=19.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=6 ttl=54 time=18.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=7 ttl=54 time=18.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=8 ttl=54 time=18.9 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=9 ttl=54 time=18.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=10 ttl=54 time=20.1 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=11 ttl=54 time=28.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=12 ttl=54 time=18.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=13 ttl=54 time=20.4 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=14 ttl=54 time=19.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=15 ttl=54 time=21.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=16 ttl=54 time=18.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=17 ttl=54 time=18.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=18 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=19 ttl=54 time=21.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=20 ttl=54 time=19.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=21 ttl=54 time=18.4 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=22 ttl=54 time=20.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=23 ttl=54 time=19.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=24 ttl=54 time=26.3 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=25 ttl=54 time=20.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=26 ttl=54 time=20.2 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=27 ttl=54 time=28.2 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=28 ttl=54 time=29.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=29 ttl=54 time=18.9 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=30 ttl=54 time=25.3 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=31 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=32 ttl=54 time=18.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=33 ttl=54 time=18.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=34 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=35 ttl=54 time=18.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=36 ttl=54 time=19.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=37 ttl=54 time=20.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=38 ttl=54 time=19.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=39 ttl=54 time=20.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=40 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=41 ttl=54 time=19.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=42 ttl=54 time=18.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=43 ttl=54 time=19.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=44 ttl=54 time=18.9 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=45 ttl=54 time=18.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=46 ttl=54 time=18.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=47 ttl=54 time=18.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=48 ttl=54 time=18.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=49 ttl=54 time=23.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=50 ttl=54 time=25.3 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=51 ttl=54 time=27.9 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=52 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=53 ttl=54 time=18.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=54 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=55 ttl=54 time=19.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=56 ttl=54 time=18.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=57 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=58 ttl=54 time=18.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=59 ttl=54 time=18.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=60 ttl=54 time=23.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=61 ttl=54 time=19.1 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=62 ttl=54 time=21.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=63 ttl=54 time=18.5 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=64 ttl=54 time=18.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=65 ttl=54 time=18.8 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=66 ttl=54 time=28.4 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=67 ttl=54 time=19.0 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=68 ttl=54 time=18.9 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=69 ttl=54 time=21.7 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=70 ttl=54 time=18.6 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=71 ttl=54 time=38.5 ms
^C
--- google.co.uk ping statistics ---
71 packets transmitted, 71 received, 0% packet loss, time 70069ms
rtt min/avg/max/mdev = 18.457/20.662/38.542/3.636 ms

0 Ratings
Reply
h3x1e
Aspiring Expert
335 Views
Message 56 of 276

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

Had another Engineer out today, explained the issue to him and as expected there's nothing Openreach can do about ping issues. My line is testing perfect for my location / distance from cabinet.

This Engineer said he would write a detailed report and advise that BT get their Wolesale Engineers to check their equipment on their nodes.

Fun fact, Openreach don't have access to BT exchange equipment, they're locked behind a keycode lock according to the OR Engineer so they cant touch any equipment in the exchange.

 

Time will tell what comes of the possible BT Wholesale Engineers findings.... if they are even assigned.

0 Ratings
Reply
h3x1e
Aspiring Expert
325 Views
Message 57 of 276

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

BT Wholesale Engineer booked out for Monday

0 Ratings
Reply
lolowalsh
Contributor
321 Views
Message 58 of 276

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

@h3x1e I escalated the problem to a special BT team they said they changed the route to where I'm connected to the servers... they said to me the changes will take at least 1 week so I will keep you updated finger crossed . I remember a guy in this forum who still posts here said they changed his route and it was fixed  and you even spoken to him

 

Next time you call BT you need to tell them to escalate your issue to a special team. Make sure to threaten to leave.

lolowalsh
Contributor
318 Views
Message 59 of 276

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

I just finished speaking to them after they called me, they even acknowledged it's a problem within the server I'm connected to so let's hope this time it's fixed for real cause I'm really tired now.

h3x1e
Aspiring Expert
309 Views
Message 60 of 276

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

Yeah my next port of call is to get this escalated, if the Wholesale Engineer doesn't find anything wrong in the exchange.