Latency Variation (Ping Spikes) during online gaming.

[h3x1e]

Making a separate thread for my own issue, and also for visibility that the issue is wide spread. 

I noticed the issue happening around the time of Battalion 1944 launch, on May 23rd ish. Thought it was their terrible netcode, so started testing some other games (FPS Games) and noticed it wasn't just Battalion, and that it seemed to be worse when watching streams during the afternoonish time and playing a game.

Connection Speed and details as follows:

VDSL2 - IFTN DSLAM

Downstaream 29.3 Mbit - 5.1SNR

Upstream 5.6 Mbit - 5.2 SNR

Current Modem and Router Setup

DrayTek Vigor 130 

Edgerouter Lite-3

----------------------------------------------------------------------------

Things tried:

Switching out the Smart Hub for my own router / modem - No Change

Resetting network Adapter on my PC to default settings - No Change

Removing all other devices form the LAN, Wired and Wireless - No Change

Connecting my PC straight to the router / modem - No Change

Playing a game without a stream on second monitor - Still get ping spikes and latency variation in games like Battalion1944, Overwatch, Patch of Exile and Battlefield 5 (10-20 ms variance without stream playing)

Forced connections to different server locations (Germany, Netherlands etc) - No Change

Tried contacting BT via Live Chat this afternoon, they had a look at my line, and immediately advised that an engineer needed to be sent out due to connection drops. I did advise them that I had restarted my modem a few times today for configuration reasons. The person again said there were errors and connection drops on my line and an engineer was needed. The engineer is coming on Friday so we'll see if he can actually find errors / noise on the line, but I doubt he / she will.

Will be trying a paid VPN to see if that makes any difference once the Engineer has been also.

Edit: Adding Trace Route to google when watching a stream:

Pinging google.co.uk [216.58.210.227] with 32 bytes of data:
Reply from 216.58.210.227: bytes=32 time=73ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=72ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=73ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=73ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=72ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=17ms TTL=54
Reply from 216.58.210.227: bytes=32 time=72ms TTL=54 - HIGH
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54
Reply from 216.58.210.227: bytes=32 time=18ms TTL=54

[h3x1e]

Woke up this morning, getting higher ping in general now..

Pinging google.co.uk [216.58.210.35] with 32 bytes of data:
Reply from 216.58.210.35: bytes=32 time=37ms TTL=54
Reply from 216.58.210.35: bytes=32 time=37ms TTL=54
Reply from 216.58.210.35: bytes=32 time=37ms TTL=54
Reply from 216.58.210.35: bytes=32 time=37ms TTL=54

That's up from 22ms normally.

Trace Route to a Path of Exile server im currently connected too.

PS C:\WINDOWS\system32> tracert -4 185.80.223.8

Tracing route to 185.80.223.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 38 ms 45 ms 93 ms 31.55.186.177 - BT Node in Leeds (seems to be the culprit for spikes at least)
4 38 ms 39 ms 38 ms 31.55.186.176
5 36 ms 36 ms 39 ms 195.99.127.96
6 34 ms 37 ms 43 ms 213.137.183.32
7 38 ms 38 ms 40 ms ldn-b9-link.telia.net [213.248.97.50]
8 43 ms 43 ms 42 ms ldn-bb3-link.telia.net [62.115.117.6]
9 45 ms 96 ms 45 ms adm-bb3-link.telia.net [62.115.113.210]
10 43 ms 44 ms 43 ms adm-b3-link.telia.net [62.115.122.179]
11 43 ms 43 ms 44 ms hostingservices-ic-335766-adm-b3.c.telia.net [62.115.37.189]
12 * * * Request timed out.
13 42 ms 42 ms 41 ms 185.80.223.8

Also noticing that none of my trace routes (bbc, google, sky, game servers) are going through the "faraday" node on the BT network anymore.

[h3x1e]

Small update of observations during a game of Battlefield 5, both watching a stream while playing and not watching a stream.

Sync Speed: 29.9Mbps D / 5.1Mbps U
Throughput: 3.4MB/s Download

Stream bandwidth usage: 900KBps

Battlefield 5 bandwidth: 20-50KB/s Down 4-6KB/s UP

Stats from inside Battlefield 5 using it's network stats display options.

Stream off  - 46-48ms / 1.6 Latency Variation / 0% Packet Loss

Stream on - 46-66ms / 10.5 Latency Variation (spiking to 20 at times) / 0% Packet Loss

So as you can see there is no Bandwidth limitation here, im barly using 10Mbps of my connection when watching a stream so there should be more than enough room for the game to stay at a lower ping when watching a stream (bandwidth wise)

[h3x1e]

Ping update from this evening 19:30.

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

Pinging google.co.uk [216.58.210.195] with 32 bytes of data:
Reply from 216.58.210.195: bytes=32 time=37ms TTL=54
Reply from 216.58.210.195: bytes=32 time=138ms TTL=54
Reply from 216.58.210.195: bytes=32 time=37ms TTL=54
Reply from 216.58.210.195: bytes=32 time=143ms TTL=54
Reply from 216.58.210.195: bytes=32 time=36ms TTL=54
Reply from 216.58.210.195: bytes=32 time=125ms TTL=54
Reply from 216.58.210.195: bytes=32 time=36ms TTL=54
Reply from 216.58.210.195: bytes=32 time=104ms TTL=54
Reply from 216.58.210.195: bytes=32 time=37ms TTL=54
Reply from 216.58.210.195: bytes=32 time=108ms TTL=54
Reply from 216.58.210.195: bytes=32 time=36ms TTL=54
Reply from 216.58.210.195: bytes=32 time=120ms TTL=54
Reply from 216.58.210.195: bytes=32 time=36ms TTL=54
Reply from 216.58.210.195: bytes=32 time=119ms TTL=54
Reply from 216.58.210.195: bytes=32 time=36ms TTL=54
Reply from 216.58.210.195: bytes=32 time=150ms TTL=54
Reply from 216.58.210.195: bytes=32 time=37ms TTL=54
Reply from 216.58.210.195: bytes=32 time=104ms TTL=54
Reply from 216.58.210.195: bytes=32 time=37ms TTL=54
Reply from 216.58.210.195: bytes=32 time=98ms TTL=54
Reply from 216.58.210.195: bytes=32 time=49ms TTL=54
Reply from 216.58.210.195: bytes=32 time=96ms TTL=54
Reply from 216.58.210.195: bytes=32 time=42ms TTL=54
Reply from 216.58.210.195: bytes=32 time=99ms TTL=54
Reply from 216.58.210.195: bytes=32 time=37ms TTL=54
Reply from 216.58.210.195: bytes=32 time=101ms TTL=54
Reply from 216.58.210.195: bytes=32 time=36ms TTL=54
Reply from 216.58.210.195: bytes=32 time=87ms TTL=54
Reply from 216.58.210.195: bytes=32 time=47ms TTL=54
Reply from 216.58.210.195: bytes=32 time=99ms TTL=54
Reply from 216.58.210.195: bytes=32 time=37ms TTL=54
Reply from 216.58.210.195: bytes=32 time=79ms TTL=54
Reply from 216.58.210.195: bytes=32 time=36ms TTL=54
Reply from 216.58.210.195: bytes=32 time=73ms TTL=54
Reply from 216.58.210.195: bytes=32 time=37ms TTL=54

Ping statistics for 216.58.210.195:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 150ms, Average = 72ms

Ping in general is still elevated from about 23ms to 37ms as you can see ping spikes almost every other send.

[h3x1e]

Noticed that after the live chat and the engineer booking that line dropped and applied Interleaving (65) on my Upstream and increased my Downstream Interleaving to 1549. 

I'm guessing that could be something to do with the base ping being so high now.

[h3x1e]

another ping to an Insurgency: Sandstorm game server located in the UK I was just playing on (experiencing the same ping spikes in game upto 120 ping)

PS C:\WINDOWS\system32> ping -4 88.202.177.43 -t

Pinging 88.202.177.43 with 32 bytes of data:
Reply from 88.202.177.43: bytes=32 time=45ms TTL=52
Reply from 88.202.177.43: bytes=32 time=131ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=144ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=153ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=150ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=156ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=90ms TTL=52
Reply from 88.202.177.43: bytes=32 time=43ms TTL=52
Reply from 88.202.177.43: bytes=32 time=139ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=152ms TTL=52
Reply from 88.202.177.43: bytes=32 time=48ms TTL=52
Reply from 88.202.177.43: bytes=32 time=144ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=165ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=169ms TTL=52
Reply from 88.202.177.43: bytes=32 time=45ms TTL=52
Reply from 88.202.177.43: bytes=32 time=160ms TTL=52
Reply from 88.202.177.43: bytes=32 time=45ms TTL=52
Reply from 88.202.177.43: bytes=32 time=137ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=153ms TTL=52
Reply from 88.202.177.43: bytes=32 time=46ms TTL=52
Reply from 88.202.177.43: bytes=32 time=150ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=138ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52
Reply from 88.202.177.43: bytes=32 time=147ms TTL=52
Reply from 88.202.177.43: bytes=32 time=44ms TTL=52

Ping statistics for 88.202.177.43:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 169ms, Average = 93ms

[h3x1e]

Update:

I got bored and just bought a VPN out of pure curiosity, it didn't help with the ping issue at all. Still spiking every other hop.

Connected to various different servers in different countries.

[h3x1e]

This mornings update:

Line dropped again and it seems like the DLM has reset or adjusted itself and the banding was taken off my line.

> vdsl status
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 36723000 bps         US Actual Rate : 5638000 bps
DS Attainable Rate : 46289016 bps US Attainable Rate : 5695170 bps
DS Path Mode : Interleave                      US Path Mode : Fast
DS Interleave Depth : 1559                   US Interleave Depth : 1
NE Current Attenuation : 25 dB           Cur SNR Margin : 1 dB
DS actual PSD : 5. 1 dB                            US actual PSD : 5. 2 dB
NE CRC Count : 0                                        FE CRC Count : 10199
NE ES Count : 0                                           FE ES Count : 9724
Xdsl Reset Times : 0                                   Xdsl Link Times : 4

ITU Version[0] : fe004452 ITU             Version[1] : 41590000
VDSL Firmware Version :                         05-07-06-0D-01-07 [with Vectoring support]
Power Management Mode :                   DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 36 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004946 CO ITU Version[1] : 544eb206
DSLAM CHIPSET VENDOR : < IFTN >

Ping issues still remain. Seeing spikes of upto 140ms when two 1080p 60fps streams are running.

Although this DLM Reset / Adjustment is good for throughput (getting 4.1MB/s up from 3.4MB/s ish) I don't expect it to last.

Will update when I get more / new info.

[h3x1e]

something weird is happening now....

DLM just dropped the connection and decreased the sync speed to 34Mbps from 36Mbps.

The latency variation on Battlefield 5 while watching a stream is not constant anymore, but it does vary up to 10-13ms but also give about 5% packet loss.

[h3x1e]

Forced to restart the modem to re-sync as we were seeing 20,000 CRC errors in a 20 minute window. Although the latency variation got slightly better (not constant) the connection was clearly very unstable.

We're back on a stable connection now, however the latency variation is back to a constant 7-15ms.