This topic

Horrible ping spikes and packet loss

Sbennett — Fri, 12 Jun 2020 15:32:25 GMT

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

Re: Horrible ping spikes and packet loss

pippincp — Fri, 12 Jun 2020 16:46:51 GMT

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

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 20:09:43 GMT

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

Re: Horrible ping spikes and packet loss

pippincp — Sat, 13 Jun 2020 20:14:09 GMT

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

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 20:30:12 GMT

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

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 20:35:56 GMT

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

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 20:41:42 GMT

--- 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

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 20:44:53 GMT

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

Re: Horrible ping spikes and packet loss

pippincp — Sat, 13 Jun 2020 21:24:58 GMT

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

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 21:31:24 GMT

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

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 21:35:13 GMT

Didn’t see it says it’s a free version after trial - downloading now

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 21:40:35 GMT

Re: Horrible ping spikes and packet loss

Sbennett — Sat, 13 Jun 2020 21:43:33 GMT

game server

Re: Horrible ping spikes and packet loss

pippincp — Sun, 14 Jun 2020 16:35:22 GMT

Is there any noise on your line? 17070 option 2, best with corded phone.

Re: Horrible ping spikes and packet loss

Sbennett — Sun, 14 Jun 2020 17:20:51 GMT

No noise

Re: Horrible ping spikes and packet loss

Sbennett — Sun, 14 Jun 2020 21:15:06 GMT

I know what the issue is - the server that is lag spiking and having packet loss is a known issue with BTs infrastructure and how they prioritise traffic -

many complaints and threads regarding it online

I’m going to call bt tomorrow if they can’t reprioritise me then I will be asking my contract to be cancelled as they won’t be supplying me with a service I can use. I never had this issue last time I was on bt it used to be rock solid.

let u know how I get on

Re: Horrible ping spikes and packet loss

Sbennett — Mon, 15 Jun 2020 09:26:38 GMT

bt have made some changes to my line - also interleaving is currently on my line which should drop off today.

will check problem again tomorrow if no improvement then i will be calling them back to release me from contract.

Re: Horrible ping spikes and packet loss

Sbennett — Thu, 18 Jun 2020 17:51:37 GMT

BT have made changes and interleaving should have stopped now - but alas im still having the same issues

I have followed advice and changed my hh to my old hh6 to see if that would reprioritise my service - but it has not

Im still getting massive ping spikes and packet loss when streaming netflix and gaming at the same time - both wired connections.

on the phone to customer service again now - see what happens if and when they answer ...... so far 35 mins no answer lol

Re: Horrible ping spikes and packet loss

Sbennett — Thu, 18 Jun 2020 18:29:49 GMT

any mods available?