High Ping on PS5 & Orbi System

[Wire_Mark]

Ok, don't know where to start with this.

A few years ago our phone line and fibre went down, Infinity 2 (upto 76mb which we did get at the time). An engineer came round and found the line dead from what I can remember. We was a new build so had two lines to the house. He swapped the lines over but we never got the 76mb like we used to. I did complain at the time but got told that 60mb was the most we could get. However my brother lives on the same street a few houses away and he is with BT and gets 74mb.

We have the home hub 6a and have been having the router drop out, vpn disconnects from working from home so I have bought the Orbi 753 system. I turned the wifi off on the HomeHub and put the Orbi system into AP mode which means I was double NATing. Ive noticed that the ping on my PS5 is now 60-80ms this is despite no matter where I check in the house the ping is roughly 18 over wifi. The PS5 is connected by ethernet into one of the Orbi satellites. 

Speed was roughly 60ish over wifi. I went through a load of troubleshooting with Orbi, they put the orbi into router mode and eventually after an hour they said I needed a modem and no router as the orbi would do that. I did some googling and found that the best idea was to get a BT HG612. I purchased one of these and have set that up, put the orbi into router mode and I have seen no change, apart from the line sync has decreased further. The ping is the same however when I do multiple pings via a terminal on macOS I get some pings coming back at over 100ms and even some packet loss.

Now, I am having issues when trying to play war zone, I don't get lobbies now upto 79ms. My brother one the same street does not have these issues. I have a three orange boxes on the screen which indicate a lag/packet loss warning I believe. I also have issues where the picture isn't rendering fully. My daughter came round who I go on war zone with and she was laughing that even hers doesn't do that. My brother doesn't have these issues when we are in the same lobby with high ping and his renders fine. He is using the Home Hub 6 also and over wifi.

I have text bt help and that comes back with I have no line issues. Well I have because this second line I was swapped to isn't as good as the first line that failed. I am really not sure what to do. I am contacting Orbi again but they are saying to contact ISP. They just told me enable bridge mode on the orbi and I asked why as the HG612 is the bridge modem and he hung up. I did it but the connection drops, when I disable the enabling of bridge mode on the Orbi the connection came back.

Any help is appreciated as I am really pulling my hair out, or could someone tell me FTTP is coming next week and I will be happy!

Connection Status		Help

Mode	VDSL2
Traffic type	PTM
DSL synchronization status	Up
DSL up time	0

Line Status   Help

Downstream Upstream Attainable rate (kbit/s) 63936 17496 SNR margin (dB) 19.4 0 Line attenuation (dB) 13.7 7.5 Output power (dBmV) 13.7 7.5   Statistics   Help     Path 0 Path 1   Downstream Upstream Downstream Upstream Line rate (kbit/s) 64991  17496  0  0  CRC errors 254  127  18  0  FEC errors 0  0  0  0  HEC errors 154  4294967290  32  0

[Wire_Mark]

Ive just done this ping test to bbc and get the following, this is on wifi right next to the Orbi Router, not one of the satellites. Hitting pings of over 200ms

PING bbc.co.uk (151.101.0.81): 56 data bytes

64 bytes from 151.101.0.81: icmp_seq=0 ttl=57 time=12.939 ms

64 bytes from 151.101.0.81: icmp_seq=1 ttl=57 time=13.535 ms

64 bytes from 151.101.0.81: icmp_seq=2 ttl=57 time=12.732 ms

64 bytes from 151.101.0.81: icmp_seq=3 ttl=57 time=14.237 ms

64 bytes from 151.101.0.81: icmp_seq=4 ttl=57 time=13.718 ms

64 bytes from 151.101.0.81: icmp_seq=5 ttl=57 time=12.906 ms

64 bytes from 151.101.0.81: icmp_seq=6 ttl=57 time=14.020 ms

64 bytes from 151.101.0.81: icmp_seq=7 ttl=57 time=14.718 ms

64 bytes from 151.101.0.81: icmp_seq=8 ttl=57 time=13.747 ms

64 bytes from 151.101.0.81: icmp_seq=9 ttl=57 time=13.693 ms

64 bytes from 151.101.0.81: icmp_seq=10 ttl=57 time=13.013 ms

64 bytes from 151.101.0.81: icmp_seq=11 ttl=57 time=13.438 ms

64 bytes from 151.101.0.81: icmp_seq=12 ttl=57 time=14.775 ms

64 bytes from 151.101.0.81: icmp_seq=13 ttl=57 time=13.014 ms

64 bytes from 151.101.0.81: icmp_seq=14 ttl=57 time=15.986 ms

64 bytes from 151.101.0.81: icmp_seq=15 ttl=57 time=14.101 ms

64 bytes from 151.101.0.81: icmp_seq=16 ttl=57 time=13.213 ms

64 bytes from 151.101.0.81: icmp_seq=17 ttl=57 time=13.967 ms

64 bytes from 151.101.0.81: icmp_seq=18 ttl=57 time=16.751 ms

64 bytes from 151.101.0.81: icmp_seq=19 ttl=57 time=15.721 ms

64 bytes from 151.101.0.81: icmp_seq=20 ttl=57 time=15.192 ms

64 bytes from 151.101.0.81: icmp_seq=21 ttl=57 time=16.543 ms

64 bytes from 151.101.0.81: icmp_seq=22 ttl=57 time=151.213 ms

64 bytes from 151.101.0.81: icmp_seq=23 ttl=57 time=198.775 ms

64 bytes from 151.101.0.81: icmp_seq=24 ttl=57 time=228.219 ms

64 bytes from 151.101.0.81: icmp_seq=25 ttl=57 time=223.593 ms

64 bytes from 151.101.0.81: icmp_seq=26 ttl=57 time=13.499 ms

64 bytes from 151.101.0.81: icmp_seq=27 ttl=57 time=30.494 ms

64 bytes from 151.101.0.81: icmp_seq=28 ttl=57 time=13.797 ms

64 bytes from 151.101.0.81: icmp_seq=29 ttl=57 time=13.273 ms

64 bytes from 151.101.0.81: icmp_seq=30 ttl=57 time=13.762 ms

64 bytes from 151.101.0.81: icmp_seq=31 ttl=57 time=12.962 ms

64 bytes from 151.101.0.81: icmp_seq=32 ttl=57 time=13.285 ms

64 bytes from 151.101.0.81: icmp_seq=33 ttl=57 time=14.532 ms

64 bytes from 151.101.0.81: icmp_seq=34 ttl=57 time=18.067 ms

64 bytes from 151.101.0.81: icmp_seq=35 ttl=57 time=23.820 ms

[Wire_Mark]

When I try running the same ping test via ethernet connected to the Orbi I get very little variation in ping 

PING bbc.co.uk (151.101.0.81): 56 data bytes

64 bytes from 151.101.0.81: icmp_seq=0 ttl=57 time=11.157 ms

64 bytes from 151.101.0.81: icmp_seq=1 ttl=57 time=11.520 ms

64 bytes from 151.101.0.81: icmp_seq=2 ttl=57 time=11.116 ms

64 bytes from 151.101.0.81: icmp_seq=3 ttl=57 time=10.800 ms

64 bytes from 151.101.0.81: icmp_seq=4 ttl=57 time=10.894 ms

64 bytes from 151.101.0.81: icmp_seq=5 ttl=57 time=11.458 ms

64 bytes from 151.101.0.81: icmp_seq=6 ttl=57 time=11.136 ms

64 bytes from 151.101.0.81: icmp_seq=7 ttl=57 time=10.936 ms

64 bytes from 151.101.0.81: icmp_seq=8 ttl=57 time=11.233 ms

64 bytes from 151.101.0.81: icmp_seq=9 ttl=57 time=11.371 ms

64 bytes from 151.101.0.81: icmp_seq=10 ttl=57 time=10.932 ms

64 bytes from 151.101.0.81: icmp_seq=11 ttl=57 time=11.019 ms

64 bytes from 151.101.0.81: icmp_seq=12 ttl=57 time=11.141 ms

64 bytes from 151.101.0.81: icmp_seq=13 ttl=57 time=11.123 ms

64 bytes from 151.101.0.81: icmp_seq=14 ttl=57 time=10.971 ms

64 bytes from 151.101.0.81: icmp_seq=15 ttl=57 time=11.122 ms

64 bytes from 151.101.0.81: icmp_seq=16 ttl=57 time=10.973 ms

64 bytes from 151.101.0.81: icmp_seq=17 ttl=57 time=11.271 ms

64 bytes from 151.101.0.81: icmp_seq=18 ttl=57 time=11.157 ms

64 bytes from 151.101.0.81: icmp_seq=19 ttl=57 time=10.951 ms

64 bytes from 151.101.0.81: icmp_seq=20 ttl=57 time=11.018 ms

64 bytes from 151.101.0.81: icmp_seq=21 ttl=57 time=11.012 ms

64 bytes from 151.101.0.81: icmp_seq=22 ttl=57 time=11.011 ms

64 bytes from 151.101.0.81: icmp_seq=23 ttl=57 time=11.275 ms

64 bytes from 151.101.0.81: icmp_seq=24 ttl=57 time=11.049 ms

64 bytes from 151.101.0.81: icmp_seq=25 ttl=57 time=10.899 ms

64 bytes from 151.101.0.81: icmp_seq=26 ttl=57 time=12.299 ms

64 bytes from 151.101.0.81: icmp_seq=27 ttl=57 time=10.952 ms

64 bytes from 151.101.0.81: icmp_seq=28 ttl=57 time=11.090 ms

64 bytes from 151.101.0.81: icmp_seq=29 ttl=57 time=11.146 ms

64 bytes from 151.101.0.81: icmp_seq=30 ttl=57 time=10.864 ms

64 bytes from 151.101.0.81: icmp_seq=31 ttl=57 time=10.869 ms

64 bytes from 151.101.0.81: icmp_seq=32 ttl=57 time=11.112 ms

64 bytes from 151.101.0.81: icmp_seq=33 ttl=57 time=11.219 ms

64 bytes from 151.101.0.81: icmp_seq=34 ttl=57 time=11.150 ms

64 bytes from 151.101.0.81: icmp_seq=35 ttl=57 time=10.881 ms

64 bytes from 151.101.0.81: icmp_seq=36 ttl=57 time=11.128 ms

64 bytes from 151.101.0.81: icmp_seq=37 ttl=57 time=11.407 ms

64 bytes from 151.101.0.81: icmp_seq=38 ttl=57 time=11.037 ms

[Wire_Mark]

Ive seen some pings going to over 1600ms over wifi

[pippincp]

Try a quiet line test, 17070 option 2, best with corded phone. The line should be silent between announcements. May get a dull hum with cordless phone.

[Wire_Mark]

It feels like there are potentially two noises on the line. But its a wireless phone so I am not sure entirely. I have just been out to the shops and there is a BT Openreach engineer at the cabinet so I stopped and spoke to him. He said the line might just need resetting so he said he would do it. He said for me to ring BT after he resets my line at some point today. He said I'll know when its reset as it will disconnect. Hopefully this will help.

[brookheather]

Your ethernet ping looks good - on wifi it is clear you have occasional interference pushing your ping above 200ms.  Try some different 5GHz wifi channels - for example try channel 100.  Try using a wifi analyzer app on your phone to see what frequencies are in use locally.  Set the Orbi to a fixed wireless channel - if it changes channel that will result in your ping increasing while it moves channel.