Horrible ping spikes and packet loss

[Sbennett]

Hi when gaming I am getting random ping spikes 200-400 ping on a U.K. server this also comes with massive packet loss although I can get packet loss when ping at 60-80.  I have done some tracerts and nothing looks out of the ordinary except a few hopes show 200 pings (bt owned ips). 

we did have some noise and low speed issues not that long ago but this was fixed - I have fibre 1

16-24Mbps . 

any help or suggestions appreciated

[pippincp]

Can you post the tracerts to the game server and bbc.co.uk?

[Sbennett]

bbc.co.uk  

  3     *        *        *     Request timed out.
  4    21 ms     *        *     2a00:2302::1100:100:33
  5     *        *        *     Request timed out.
  6    25 ms    22 ms    21 ms  peer8-et7-0-0.telehouse.ukcore.bt.net [2a00:2380:c::31f]
  7    22 ms    22 ms    56 ms  2620:11a:c000:357:fa57::
  8    52 ms    76 ms    42 ms  2a04:4e42::81

game server

  3     *       20 ms    20 ms  31.55.186.177
  4    20 ms    20 ms    22 ms  31.55.186.184
  5    80 ms    76 ms    81 ms  core3-hu0-6-0-3.faraday.ukcore.bt.net [195.99.127.194]
  6    79 ms    58 ms    51 ms  166-49-209-132.gia.bt.net [166.49.209.132]
  7    84 ms    85 ms    87 ms  t2c3-et-7-1-0.nl-ams2.gia.bt.net [166.49.195.170]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    34 ms    39 ms    88 ms  po2.agr1-dedi-m1.bb.as24961.net [62.141.47.157]
 11    64 ms    48 ms    53 ms  81.30.148.30

omitted few couple of hops under 10ms

[pippincp]

They don't show any packet loss or a horrible ping to Germany. Try a pingplotter trace.

[Sbennett]

Pinging www.bbc.net.uk [212.58.233.251] with 1024 bytes of data:
Reply from 212.58.233.251: bytes=1024 time=23ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=45ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=23ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=30ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=74ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=75ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=80ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=69ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=69ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=90ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=36ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=81ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=25ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=47ms TTL=52
Request timed out.
Reply from 212.58.233.251: bytes=1024 time=23ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=23ms TTL=52
Reply from 212.58.233.251: bytes=1024 time=35ms TTL=52
Request timed out.
Reply from 212.58.233.251: bytes=1024 time=85ms TTL=52

Ping statistics for 212.58.233.251:
    Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 90ms, Average = 51ms

now the game server

Pinging 81.30.148.30 with 1024 bytes of data:
Reply from 81.30.148.30: bytes=1024 time=93ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=58ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=42ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=36ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=39ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=104ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=38ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=69ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=40ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=37ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=72ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=51ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=67ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=175ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=69ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=80ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=95ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=36ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=53ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=48ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=51ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=47ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=42ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=36ms TTL=54

Ping statistics for 81.30.148.30:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 175ms, Average = 56ms

[Sbennett]

Pinging 81.30.148.30 with 1024 bytes of data:
Reply from 81.30.148.30: bytes=1024 time=64ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=97ms TTL=54
Request timed out.
Request timed out.
Reply from 81.30.148.30: bytes=1024 time=87ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=74ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=66ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=98ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=64ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=88ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=120ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=40ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=60ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=120ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=71ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=36ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=36ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=38ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=56ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=37ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=37ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=36ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=41ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=37ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=37ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54
Reply from 81.30.148.30: bytes=1024 time=35ms TTL=54

Ping statistics for 81.30.148.30:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 120ms, Average = 57ms

[Sbennett]

--- PING 81.30.148.30 (81.30.148.30) 56(84) bytes of data. ---

--- 81.30.148.30 ping statistics ---

packets transmitted
9
received
0
packet loss
100 %
time
307 ms

[Sbennett]

https://www.netmeter.co.uk/ping-test/202023-143337-c177.html

[pippincp]

You've educated me, I never knew pingplotter looked like that. Thankyou.

[Sbennett]

Didn’t use ping plotter as u can tell - didn’t fancy a trial or paying for it unless there is a free version