cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
980 Views
Message 1 of 6

Re: Ping spikes making online gaming unplayable

Hi Neil, could you also DM me to escalate this issue, I'm experiencing the same issues in my new flat, here's an example when I ping google.com, it's probably a faulty line as I was using the same hub in my previous flat and everything was working perfectly.

Reply from 2a00:1450:4009:809::200e: time=16ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=36ms
Reply from 2a00:1450:4009:809::200e: time=7ms
Reply from 2a00:1450:4009:809::200e: time=51ms
Reply from 2a00:1450:4009:809::200e: time=39ms
Reply from 2a00:1450:4009:809::200e: time=36ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=58ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=39ms
Reply from 2a00:1450:4009:809::200e: time=41ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=74ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=37ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=34ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=43ms
Reply from 2a00:1450:4009:809::200e: time=6ms
Reply from 2a00:1450:4009:809::200e: time=7ms

0 Ratings
5 REPLIES 5
955 Views
Message 2 of 6

Re: Ping spikes making online gaming unplayable

 

Hi @amstee, I've started your own thread so you can get help from the community. Can you run a tracert command instead as the ping plotter as it doesn't really help us see if there is a problem on the network?

 

Also posting your router stats will help us understand if there is a fault with the line.  your Home Hub router stats and we'll take a look? You'll get them by entering 192.168.1.254 in your browser, if you have a home hub 5 please go to troubleshooting then helpdesk and if its a Smart Hub go to advanced settings then technical log information. I'd also recommend you do a quiet line test? - dial 17070 option 2 it should be silent.

937 Views
Message 3 of 6

Re: Ping spikes making online gaming unplayable

Here are my tech log infromation.

Product name BT Smart Hub 2
Serial number +091299+1838005168
Fireware version v0.21.03.07094-BT (Thu Jul 9 17:43:55 2020)
Board version R01
GUI version 1.56 15_02_2019
DSL uptime 0 days 19 Hours 32 Mins 7 Secs
Data rate 10.0 Mbps / 55.0 Mbps
Maximum Data rate 15.9 Mbps / 59.1 Mbps
Noise margin 9.5/6.9
Line attenuation 8.8/18.3
Signal attenuation 8.8/19.8
VLAN id 101
Upstream error control Off
Downstream error control Off
Data sent / received 804.1 MB Uploaded / 2.1 GB Downloaded
Broadband username bthomehub@btbroadband.com
BT Wi-Fi Active
2.4 GHz wireless network name EmBarn
2.4 GHz wireless channel Smart (Channel11)
5 GHz wireless network name EmBarn
5 GHz wireless channel Smart (Channel36)
Wireless Security WPA2 (Recommanded)
Wireless mode Mode 1
Firewall On
MAC address 4C:1B:86:D4:8E:15
Software variant -
Boot loader 0.1.7-BT (Thu Nov 30 09:45:22 2017)

My connection seems to be a lot more stable this morning compared to yesterday
0 Ratings
936 Views
Message 4 of 6

Re: Ping spikes making online gaming unplayable

C:\Users\jerem>tracert google.com

Tracing route to google.com [2a00:1450:4009:816::200e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 3 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 6 ms 5 ms 5 ms 2a00:2302::2:100:16
4 6 ms 6 ms 6 ms 2a00:2302::2:100:37
5 * * * Request timed out.
6 7 ms 7 ms 7 ms 2a00:2380:14::8f
7 6 ms 5 ms 5 ms 2a00:2380:2001:7000::17
8 * 7 ms * 2a00:1450:80f1::1
9 9 ms * 10 ms 2001:4860:0:1::41dc
10 14 ms * * 2001:4860:0:1::2f81
11 5 ms 5 ms 6 ms lhr25s25-in-x0e.1e100.net [2a00:1450:4009:816::200e]

Trace complete.

C:\Users\jerem>tracert google.com

Tracing route to google.com [2a00:1450:4009:80b::200e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 3 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 4 ms 4 ms 4 ms 2a00:2302::2:100:16
4 5 ms 5 ms 5 ms 2a00:2302::2:100:2f
5 5 ms 4 ms 5 ms 2a00:2380:3014:9000::3c
6 6 ms 4 ms 4 ms 2a00:2380:14::bd
7 5 ms 4 ms 4 ms 2a00:2380:2001:7000::17
8 7 ms 6 ms 6 ms 2a00:1450:8103::1
9 6 ms * * 2001:4860:0:135e::1
10 6 ms 6 ms 5 ms 2001:4860:0:135e::13
11 6 ms 6 ms 6 ms 2607:f8b0:e000:8000::6
12 7 ms 6 ms 6 ms 2001:4860::9:4001:45d3
13 6 ms 7 ms 6 ms 2001:4860:0:1100::1
14 * 7 ms * 2001:4860:0:1::41ab
15 6 ms 6 ms 6 ms lhr25s28-in-x0e.1e100.net [2a00:1450:4009:80b::200e]

Trace complete.

C:\Users\jerem>tracert google.com

Tracing route to google.com [2a00:1450:4009:80b::200e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 3 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 4 ms 4 ms 4 ms 2a00:2302::2:100:16
4 5 ms 5 ms 5 ms 2a00:2302::2:100:2f
5 4 ms 4 ms 4 ms 2a00:2380:3014:9000::3c
6 4 ms 5 ms 5 ms 2a00:2380:14::bd
7 5 ms 5 ms 5 ms 2a00:2380:2001:7000::17
8 7 ms 6 ms 6 ms 2a00:1450:8103::1
9 6 ms 6 ms 6 ms 2001:4860:0:135e::1
10 6 ms * 6 ms 2001:4860:0:135e::13
11 6 ms 5 ms 6 ms 2607:f8b0:e000:8000::6
12 7 ms 7 ms 7 ms 2001:4860::9:4001:45d3
13 6 ms 6 ms 7 ms 2001:4860:0:1100::1
14 7 ms 7 ms * 2001:4860:0:1::41ab
15 6 ms 6 ms 6 ms lhr25s28-in-x0e.1e100.net [2a00:1450:4009:80b::200e]

Trace complete.

C:\Users\jerem>tracert google.com

Tracing route to google.com [2a00:1450:4009:80b::200e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 3 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 4 ms 5 ms 4 ms 2a00:2302::2:100:16
4 5 ms 5 ms 4 ms 2a00:2302::2:100:2f
5 4 ms 4 ms 4 ms 2a00:2380:3014:9000::3c
6 5 ms 5 ms 5 ms 2a00:2380:14::bd
7 5 ms 4 ms 5 ms 2a00:2380:2001:7000::17
8 6 ms 6 ms 6 ms 2a00:1450:8103::1
9 6 ms 6 ms 6 ms 2001:4860:0:135e::1
10 * 5 ms 5 ms 2001:4860:0:135e::13
11 6 ms 6 ms 7 ms 2607:f8b0:e000:8000::6
12 7 ms 7 ms 7 ms 2001:4860::9:4001:45d3
13 6 ms 6 ms 6 ms 2001:4860:0:1100::1
14 7 ms * * 2001:4860:0:1::41ab
15 6 ms 6 ms 6 ms lhr25s28-in-x0e.1e100.net [2a00:1450:4009:80b::200e]

Trace complete.

C:\Users\jerem>tracert google.com

Tracing route to google.com [2a00:1450:4009:80b::200e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 4 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 4 ms 4 ms 4 ms 2a00:2302::2:100:16
4 6 ms 5 ms 4 ms 2a00:2302::2:100:2f
5 5 ms 5 ms 5 ms 2a00:2380:3014:9000::3c
6 5 ms 5 ms 5 ms 2a00:2380:14::bd
7 4 ms 4 ms 4 ms 2a00:2380:2001:7000::17
8 6 ms 6 ms 6 ms 2a00:1450:8103::1
9 6 ms 6 ms * 2001:4860:0:135e::1
10 5 ms 5 ms * 2001:4860:0:135e::13
11 6 ms 6 ms 6 ms 2607:f8b0:e000:8000::6
12 7 ms 7 ms 8 ms 2001:4860::9:4001:45d3
13 7 ms 6 ms 6 ms 2001:4860:0:1100::1
14 * 7 ms * 2001:4860:0:1::41ab
15 6 ms 6 ms 6 ms lhr25s28-in-x0e.1e100.net [2a00:1450:4009:80b::200e]
0 Ratings
920 Views
Message 5 of 6

Re: Ping spikes making online gaming unplayable

Hi, @amstee many thanks for doing the checks, those results look great at the moment. If you notice any further issues do a few tracerts as that will show which hop the delay is on. 

0 Ratings
887 Views
Message 6 of 6

Re: Ping spikes making online gaming unplayable

Hey I've been experiencing the same issue tonight here is the output of a few traceroute commands, I feel like this unstability is due to traffic in my area ? I'm not downloading or uploading anything.

C:\Users\jerem>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 31 ms 41 ms 36 ms 2a00:2302::3:203:2be
3 7 ms 6 ms 7 ms 2a00:2302::2:100:16
4 7 ms 7 ms 7 ms 2a00:2302::2:100:17
5 6 ms * 6 ms 2a00:2380:3014:8000::10
6 52 ms 75 ms 83 ms peer7-et7-0-2.telehouse.ukcore.bt.net [2a00:2380:14::71]
7 6 ms 6 ms 5 ms 2a00:2380:2001:7000::1d
8 5 ms 5 ms 5 ms 2a04:4e42:600::81

Trace complete.

C:\Users\jerem>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 3 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 54 ms 57 ms 60 ms 2a00:2302::2:100:16
4 60 ms 58 ms 56 ms 2a00:2302::2:100:17
5 6 ms 6 ms 6 ms 2a00:2380:3014:8000::10
6 43 ms 59 ms 58 ms peer7-et7-0-2.telehouse.ukcore.bt.net [2a00:2380:14::71]
7 6 ms 6 ms 6 ms 2a00:2380:2001:7000::1d
8 5 ms 5 ms 5 ms 2a04:4e42:600::81

Trace complete.

C:\Users\jerem>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 63 ms 53 ms 55 ms 2a00:2302::3:203:2be
3 10 ms 6 ms 6 ms 2a00:2302::2:100:16
4 47 ms 37 ms 30 ms 2a00:2302::2:100:17
5 6 ms * 6 ms 2a00:2380:3014:8000::10
6 38 ms 16 ms 49 ms peer7-et7-0-2.telehouse.ukcore.bt.net [2a00:2380:14::71]
7 6 ms 6 ms 6 ms 2a00:2380:2001:7000::1d
8 5 ms 5 ms 6 ms 2a04:4e42:600::81

Trace complete.

C:\Users\jerem>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 3 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 6 ms 7 ms 7 ms 2a00:2302::2:100:16
4 60 ms 46 ms 67 ms 2a00:2302::2:100:17
5 6 ms 6 ms 6 ms 2a00:2380:3014:8000::10
6 6 ms 6 ms 6 ms peer7-et7-0-2.telehouse.ukcore.bt.net [2a00:2380:14::71]
7 6 ms 5 ms 6 ms 2a00:2380:2001:7000::1d
8 5 ms 6 ms 5 ms 2a04:4e42:600::81

Trace complete.

C:\Users\jerem>tracert google.com

Tracing route to google.com [2a00:1450:4009:800::200e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 4 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 44 ms 45 ms 48 ms 2a00:2302::2:100:16
4 5 ms 5 ms 5 ms 2a00:2302::2:100:1f
5 5 ms 4 ms 4 ms 2a00:2380:3014:9000::10
6 5 ms 6 ms 5 ms peer2-et0-1-5.slough.ukcore.bt.net [2a00:2380:14::57]
7 42 ms 50 ms 48 ms 2a00:2380:2015:2000::13
8 6 ms 5 ms 6 ms 2a00:1450:80ff::1
9 52 ms 61 ms 35 ms 2001:4860:0:1::2fe2
10 34 ms 34 ms 20 ms 2001:4860:0:135d::12
11 * * 64 ms 2001:4860::c:4000:dd7a
12 49 ms 8 ms 5 ms 2001:4860::9:4001:45d3
13 6 ms 6 ms 6 ms 2001:4860:0:1100::1
14 22 ms 6 ms 5 ms 2001:4860:0:1::419
15 6 ms 5 ms 5 ms lhr25s11-in-x0e.1e100.net [2a00:1450:4009:800::200e]

Trace complete.

C:\Users\jerem>tracert google.com

Tracing route to google.com [2a00:1450:4009:800::200e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms broadband.bt.com [2a00:23c2:8684:cd01:4e1b:86ff:fed4:8e15]
2 3 ms 3 ms 3 ms 2a00:2302::3:203:2be
3 5 ms 5 ms 5 ms 2a00:2302::2:100:16
4 52 ms 41 ms 60 ms 2a00:2302::2:100:1f
5 4 ms 4 ms 4 ms 2a00:2380:3014:9000::10
6 6 ms 5 ms 5 ms peer2-et0-1-5.slough.ukcore.bt.net [2a00:2380:14::57]
7 5 ms 5 ms 5 ms 2a00:2380:2015:2000::13
8 * * 6 ms 2a00:1450:80ff::1
9 6 ms 5 ms 5 ms 2001:4860:0:1::2fe2
10 7 ms 6 ms 7 ms 2001:4860:0:135d::12
11 8 ms 8 ms * 2001:4860::c:4000:dd7a
12 5 ms 6 ms 7 ms 2001:4860::9:4001:45d3
13 69 ms 60 ms 78 ms 2001:4860:0:1100::1
14 5 ms 5 ms 17 ms 2001:4860:0:1::419
15 37 ms 36 ms 25 ms lhr25s11-in-x0e.1e100.net [2a00:1450:4009:800::200e]

Trace complete.
0 Ratings