cancel
Showing results for 
Search instead for 
Did you mean: 
Jimbobjr88
Newbie
477 Views
Message 1 of 5

Ping keeps spiking whilst gaming - Infinity 2 Connection

Hi all,

 

Just looking for a bit of help and/or assistance really. About 5/6 weeks ago I noticed that my ping would spike substantially whilst gaming, up over 300/400ms which would inevitably result in me getting the boot from most servers. I play on European servers, mainly UK but some German, French, Dutch, etc. locations that I would describe as being geographically close by in terms of sending/receiving data packets. 

 

Now, I've nearly had my Infinity 2 connection for 2 years and up until about 6 weeks weeks ago it has been flawless. I would have a constant ping of high "teens" to low 20's on most servers that I played on. This would be rock solid with barely any fluctuation. 

 

My network at home consists currently of a BT Home Hub 5 which is downstairs, about 2 metres from the wall socket. I have a 30 meter CAT5e cable running upstairs into the spare room which usually plugs into an unmanaged switch and from there I have 2 PC's, a laptop, PS4 and Raspberry Pi connected to the switch via ethernet cables. Like I said, this setup has been working great since as long as I can remember. 

 

If I remember rightly, and this sounds crazy but the problems seemed to start after my machines were losing internet connectivity. The DHCP server on the HH5 seemed to mess up and it was serving out 192.168.1.1 as the default gateway. This issue was also present on wireless devices on the network. Applying static IP's would rectify the issue slightly but not completely. They were still losing internet connectivity on a regular basis. I tried factory resetting the HH5, power resetting, etc. to no avail, this internet connectivity issue would just keep returning. I decided to just go out and buy another VDSL2 router as I don't like the restrictiveness of HH5 anyway so I treated myself to an Asus DSL-AC68U which solved my DHCP/internet connectivity issues at the very least but I was having even more issues with my connection using this device. 

 

The BT Infinity 2 profile on the router doesn't seem to be configured correctly as I was getting crazy amounts of CRC errors on the down and upstream communication channels. I tried a few combinations of settings found on this forum but I just couldn't get the thing to play nicely. Oh, it was also limiting my connection to 56mbps downstream too =l I confess, there are more settings on this router than I know what to do with so if anybody can suggest a custom settings profile I am more than willing to try it as I still have the router. 

 

Anyway, I'm now back using the HH5, after changing the router IP to 192.168.1.1 DHCP is working. I assume it's still sending out the default gateway of 192.168.1.1 but it no longer matters. Plus I'm also getting my full sync speed of 75mbps downstream again. 

 

A friend from work is lending me a spare, working HH5 tomorrow so I will swap it out and see if that resolves anything but I'm completely stuck at the moment. I literally do not know what to do. I contacted customer support but they weren't of any use at all 😞

 

My current setup at the time of writing this message is, wireless turned off with my machine plugged directly into the HH5 with nothing else on the network. The switch has been removed from the equation and all other devices but still, my spiking pings continue 😞

 

My router stats are below:-

 

1. Product name:BT Home Hub
2. Serial number:+068343+NQ34831920
3. Firmware version:Software version 4.7.5.1.83.8.204.1.11 (Type A) Last updated 01/07/15
4. Board version:BT Hub 5A
5. DSL uptime:0 days, 16:11:34
6. Data rate:19999 / 75730
7. Maximum data rate:28446 / 79171
8. Noise margin:14.9 / 6.4
9. Line attenuation:15.8 / 14.8
10. Signal attenuation:15.8 / 14.8
11. Data sent/received:1.4 GB / 22.8 GB
12. Broadband username:bthomehub@btbroadband.com
13. BT Wi-fi:Yes
14. 2.4 GHz Wireless network/SSID:BTHub5-XQ5K
15. 2.4 GHz Wireless connections:Disabled
16. 2.4 GHz Wireless security:WPA2
17. 2.4 GHz Wireless channel:Automatic (Smart Wireless)
18. 5 GHz Wireless network/SSID:BTHub5-XQ5K
19. 5 GHz Wireless connections:Disabled
20. 5 GHz Wireless security:WPA2
21. 5 GHz Wireless channel:Automatic (Smart Wireless)
22. Firewall:Default
23. MAC Address:18:62:2c:6b:34:bc
24. Modulation:G.993.2 Annex B
25. Software variant:AA
26. Boot loader:1.0.0

 

Here is a bit of snippet of me pinging a BF4 server earlier this evening whilst attempting to play. I know you won't be able to draw much from this but at least it demonstrates my ping issues. Please note, I had nothing using the network at this point, except from my machine playing BF4...

 

Reply from 85.114.153.132: bytes=32 time=42ms TTL=113
Reply from 85.114.153.132: bytes=32 time=123ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=122ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=35ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=36ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=170ms TTL=113
Reply from 85.114.153.132: bytes=32 time=35ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=175ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=35ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=193ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=38ms TTL=113
Reply from 85.114.153.132: bytes=32 time=213ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=440ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=41ms TTL=113
Reply from 85.114.153.132: bytes=32 time=211ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=47ms TTL=113
Reply from 85.114.153.132: bytes=32 time=218ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=35ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=61ms TTL=113
Reply from 85.114.153.132: bytes=32 time=235ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=105ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=35ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=81ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=94ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=36ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=95ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=88ms TTL=113
Reply from 85.114.153.132: bytes=32 time=34ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=119ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=176ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=32ms TTL=113
Reply from 85.114.153.132: bytes=32 time=36ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=194ms TTL=113
Reply from 85.114.153.132: bytes=32 time=30ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=31ms TTL=113
Reply from 85.114.153.132: bytes=32 time=33ms TTL=113
Reply from 85.114.153.132: bytes=32 time=202ms TTL=113

 

Any help would be greatly appreciated! Well done if you've got this far by the way 😄

 

Cheers

0 Ratings
Reply
4 REPLIES 4
Rottie
Expert
471 Views
Message 2 of 5

Re: Ping keeps spiking whilst gaming - Infinity 2 Connection

Not sure how much this will help or otherwise, but below are my traceroute and ping results to the server you mentioned in your OP. I'm in Docklands, London (Albert Dock Exchange / LDNAK) and I'm on Infinity 2.

 

Last login: Tue Oct  6 20:15:02 on console
Runabout:~ Kev$ ping -c 10 85.114.153.132
PING 85.114.153.132 (85.114.153.132): 56 data bytes
64 bytes from 85.114.153.132: icmp_seq=0 ttl=113 time=22.372 ms
64 bytes from 85.114.153.132: icmp_seq=1 ttl=113 time=22.379 ms
64 bytes from 85.114.153.132: icmp_seq=2 ttl=113 time=23.159 ms
64 bytes from 85.114.153.132: icmp_seq=3 ttl=113 time=23.942 ms
64 bytes from 85.114.153.132: icmp_seq=4 ttl=113 time=23.263 ms
64 bytes from 85.114.153.132: icmp_seq=5 ttl=113 time=22.568 ms
64 bytes from 85.114.153.132: icmp_seq=6 ttl=113 time=22.516 ms
64 bytes from 85.114.153.132: icmp_seq=7 ttl=113 time=22.310 ms
64 bytes from 85.114.153.132: icmp_seq=8 ttl=113 time=22.609 ms
64 bytes from 85.114.153.132: icmp_seq=9 ttl=113 time=22.544 ms

--- 85.114.153.132 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.310/22.766/23.942/0.497 ms
Runabout:~ Kev$ traceroute -I 85.114.153.132
traceroute to 85.114.153.132 (85.114.153.132), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  2.632 ms  0.955 ms  0.789 ms
 2  217.32.146.68 (217.32.146.68)  5.714 ms  6.780 ms  5.662 ms
 3  217.32.146.94 (217.32.146.94)  5.782 ms  6.675 ms  6.654 ms
 4  217.32.147.202 (217.32.147.202)  7.262 ms  7.472 ms  6.383 ms
 5  213.120.178.67 (213.120.178.67)  6.997 ms  6.899 ms  6.378 ms
 6  217.41.168.107 (217.41.168.107)  7.539 ms  9.015 ms  7.887 ms
 7  109.159.249.114 (109.159.249.114)  7.062 ms  6.982 ms  6.728 ms
 8  core4-te0-0-0-26.faraday.ukcore.bt.net (109.159.249.57)  6.713 ms  6.418 ms  7.107 ms
 9  peer1-xe-11-1-0.faraday.ukcore.bt.net (213.121.193.181)  7.415 ms  7.328 ms  8.960 ms
10  195.99.126.154 (195.99.126.154)  7.507 ms  7.444 ms  7.469 ms
11  * * *
12  78.152.76.108 (78.152.76.108)  18.072 ms  16.643 ms  16.706 ms
13  * * *
14  ae0.edge1.dus1.de.as5580.net (78.152.35.81)  22.598 ms  16.825 ms  16.835 ms
15  78.152.32.59 (78.152.32.59)  16.697 ms  16.097 ms  16.378 ms
16  ve531.ae10.brip-a.dus1-de.myloc.de (62.141.47.185)  31.889 ms  30.575 ms  26.188 ms
17  85.114.153.132.gamed-server.de (85.114.153.132)  21.533 ms  21.844 ms  22.992 ms
Runabout:~ Kev$ 
0 Ratings
Reply
Jimbobjr88
Newbie
463 Views
Message 3 of 5

Re: Ping keeps spiking whilst gaming - Infinity 2 Connection

Hi Rottie,

 

Please see my trace route below. It doesn't look bad which is probably even worse, an intermittent issue - great!

 

Tracing route to 85.144.153.132 over a maximum of 30 hops

1 3 ms 1 ms 1 ms Unknown-00-1d-aa-b1-2f-e0.home [192.168.1.1]
2 7 ms 7 ms 9 ms 217.32.143.229
3 10 ms 8 ms 8 ms 217.32.144.14
4 10 ms 9 ms 9 ms 212.140.235.106
5 10 ms 9 ms 9 ms 217.41.169.169
6 10 ms 9 ms 9 ms 213.120.179.81
7 9 ms 9 ms 9 ms acc1-xe-5-0-3.sf.21cn-ipp.bt.net [109.159.251.113]
8 17 ms 15 ms 15 ms core1-te-0-4-0-16.ilford.ukcore.bt.net [109.159.251.51]
9 16 ms 15 ms 15 ms peer1-xe3-0-0.telehouse.ukcore.bt.net [109.159.254.215]
10 17 ms 17 ms 17 ms linx.iptp.net [195.66.225.64]
11 21 ms 21 ms 21 ms be10.r0.r327.nkf.ams.nl.iptp.net [91.194.117.195]
12 22 ms 21 ms 24 ms 4-4.r0.r327.nkf.ams.nl.iptp.net [176.56.179.137]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.

0 Ratings
Reply
Rottie
Expert
454 Views
Message 4 of 5

Re: Ping keeps spiking whilst gaming - Infinity 2 Connection

Hi again,

 

As you say, it's harder to diagnose an intermittent fault than it is to diagnose one that manifests itself all the time.

 

Have you considered using a connection monitoring tool, such as thinkbroadband's BQM (Broadband Quality Meter), which will enable you to monitor your connection's latency and packet loss, in almost real-time?

 

 

0 Ratings
Reply
Jimbobjr88
Newbie
443 Views
Message 5 of 5

Re: Ping keeps spiking whilst gaming - Infinity 2 Connection

Indeed. I haven't as of yet but I will give it a go. 

 

Just as a side note, I've just managed to play a couple of games of BF4 on Dutch servers for 1 hour with a constant ping of 27ms which is pretty much what it used to be. I've not been able to do this for weeks, as previously mentioned... Perhaps BT are watching my post haha.

 

Cheers, I'll post back my results; helpful or otherwise. 

 

Any advance on settings for the Asus AC68U though anybody? I really would love to start using this as my router instead of the HH5... 😄

 

0 Ratings
Reply