High Ping spikes

[SlippinJimmy]

I'm on gigabit full fibre. Download and upload speeds are as advertised and i'm happy with, but my latency is all over the place, which I notice when playing multiplayer games. When running a ping within command prompt or tracert, sometimes the ping times out, but often shows high latency. I'm running ethernet to the router. This issue started about a month ago, and i've been with EE for 2 months or so. I've also tried my own mesh system in place of the EE router, same issue.

I rang them up, but all they did was try change the wifi security (Nothing to do with the ethernet connection) and send out a new Ethernet cable, but this issue is happening on more than one device.

Any ideas or next steps to try resolve this? i'm almost certain this is on the Openreach side, but they said they're getting an 'all good' from the Openreach side, so cannot raise an issue with them.

[XRaySpeX]

Servers along the tracert have better things to do than respond to your arbitrary pings, namely their own job & routing that they are there for. The only thing that matters is the final target node.

[SlippinJimmy]

Okay fair enough. But surely the second screenshot with pings to Google show the spikes? It aligns when my in-game ping spikes also

[XRaySpeX]

So it was busy with its own work from time to time.

[JimM11]

@SlippinJimmy Turn the wifi off and see if it is still the same on Ethernet only, tracert does not really help with the ping response as that gateway may be getting on doing what is needed. Run packetloss see picture linked.

Re: ping - The EE Community

https://packetlosstest.com

Ping statistics for 2a00:1450:4009:c0f::64: to google on iPv6 wifi connected, will post up Ethernet tomorrow.
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 26ms, Average = 20ms

Ping statistics for 2a04:4e42:400::81: to BBC on iPv6 as above
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 16ms, Average = 12ms

[JimM11]

@SlippinJimmy Ethernet connected ping below and will do a MTR as well. time test at 8.16am.

Ping statistics for 2a04:4e42:200::81:   To the BBC.co.uk on Ethernet
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 12ms, Average = 11ms

MTR results, very like tracert, 8.26am to bbc.co.uk, 1st and last is all that matters. Asus Router to the BBC server.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| ZenWiFi_XT8-BBD0 - 0 | 107 | 107 | 0 | 0 | 1 | 0 |
| 90.247.xxx.x - 5 | 92 | 88 | 3 | 184 | 382 | 173 |
| 63.130.xxx.xx - 48 | 38 | 20 | 0 | 11 | 12 | 11 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| 151.101.xxx.xx - 0 | 107 | 107 | 10 | 11 | 12 | 10 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Tracing route to bbc.co.uk [2a04:4e42:200::81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2a0a:ef40:xxxx:xxxx::1
2 270 ms 242 ms 271 ms 2a0a:xxxx:xxxx:16::1
3 13 ms * * 2a0a:ef40:xxxx:xxx::1
4 * * * Request timed out.
5 11 ms 11 ms 11 ms 2a04:xxxx:xx::xx

Tracing route to one.one.one.one [1.0.0.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ZenWiFi_XT8-BBD0 [192.168.50.x]
2 246 ms 199 ms 172 ms 90.247.xxx.x
3 * 10 ms * 63.130.xxx.xx
4 13 ms 11 ms 11 ms 90.255.xxx.xx
5 18 ms 11 ms 10 ms 162.158.xx.x
6 11 ms 10 ms 12 ms one.one.one.one [1.0.0.1]