Ask
Reply
Solution
22-06-2022 12:21 PM
I used to get 5ms ping to London (from Coventry), now I am being auto connected to Edinburugh and I get 15 ping to there, when I try to speedtest to London or even right next to me in Leicester I am getting pings above 22...I called in and they just said "they added new servers and there's nothing much we can do"...
any help?
22-07-2022 07:32 AM - edited 22-07-2022 07:33 AM
Speed test on a Raspberry Pi connected directly into the router via an ethernet cable:
Sadly I can't find the speed test server ID for the Vodafone Bracknell server so I used the Acton (Greater London) one for the above test.
Speed test on an Apple MacBook Pro connected via 5GHz wifi:
I'll see how remote working goes, I was having problems with stuttering on calls and sluggishness with remote desktops which sometimes froze like it did yesterday.
22-07-2022 07:46 AM - edited 22-07-2022 08:00 AM
Found the Vodafone Bracknell server ID and re-ran the test using that on the Raspberry Pi with the direct ethernet connection to the router.
I don't know whether or not this followed on from my chat with the chap from yesterday or if there was a wider fix going on anyway, I'm interested to see if anyone else had their routing fixed last night.
It also remains to be seen whether this stays put, as I've seen some of you being put on the correct gateway only for it to go back to the 'wrong' one.
22-07-2022 11:35 AM
I knew it was too good to be true
Here's a traceroute from earlier when I was on the correct BNG
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 _gateway (192.168.1.1) 0.920 ms 0.937 ms 0.972 ms
2 * * *
3 63.130.127.213 (63.130.127.213) 6.010 ms 5.991 ms 5.978 ms
4 10.200.18.45 (10.200.18.45) 5.962 ms 5.983 ms 5.895 ms
5 63.130.105.130 (63.130.105.130) 7.344 ms 7.230 ms 7.203 ms
6 90.255.251.33 (90.255.251.33) 8.532 ms 7.611 ms 7.216 ms
7 172.70.94.2 (172.70.94.2) 7.892 ms 172.70.87.2 (172.70.87.2) 37.043 ms 172.70.160.2 (172.70.160.2) 6.830 ms
8 one.one.one.one (1.1.1.1) 6.969 ms 6.701 ms 6.830 ms
I was on a teams call earlier and the connection dropped for a few minutes....
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 _gateway (192.168.1.1) 0.891 ms 0.808 ms 0.739 ms
2 192.168.0.1 (192.168.0.1) 1.496 ms 1.531 ms 1.510 ms
3 * * *
4 192.168.213.21 (192.168.213.21) 44.946 ms 44.891 ms 44.785 ms
5 192.168.213.22 (192.168.213.22) 37.659 ms 37.626 ms 37.434 ms
6 * * *
7 * * *
8 63.130.105.110 (63.130.105.110) 37.381 ms 36.930 ms 37.764 ms
9 * * *
10 90.255.251.37 (90.255.251.37) 43.195 ms 28.545 ms 31.414 ms
11 162.158.32.11 (162.158.32.11) 30.767 ms 29.799 ms 34.780 ms
12 one.one.one.one (1.1.1.1) 30.899 ms 34.744 ms 29.927 ms
Looks like I'm back on the Manchester BNG again! It was great whilst it lasted... just didn't expect it to go back so quickly!
9.|-- ae34-xcr1.ltw.cw.net (195.2.8.45) 10.|-- ae8-xcr1.man.cw.net (195.2.9.98)
22-07-2022 11:49 AM
Actually my FTTP connection has gone down completely - I'm on the 4G backup dongle now. Never a dull day.
22-07-2022 12:01 PM
@Gerry_Atric wrote:Actually my FTTP connection has gone down completely - I'm on the 4G backup dongle now. Never a dull day.
Gerry, if you remember what happened to me then you know this is normal. This was what happened before mine got fixed, it's going to switch back and forth and you will get some disconnects for 1-3 days then hopefully it'll resolve for you (just like how I was commenting about being put on London, then back to Scotland, then to Bracknell, then back to London).
22-07-2022 12:17 PM
Thanks for the reminder - I completely forgot. I got myself into a panic because I'm working from home and was in the middle of an important call with someone. When the connection returned I thought it was still going through the FTTP connection but was in fact using the 4G dongle. The latency jumped up as expected but I thought it was the wrong BNG via FTTP!
I don't mind things being fiddled with out of hours but not so keen on it being during the working day 😞
Still, if it eventually resolves itself permanently eventually, I guess it's worth it.
So are you happy with things since, including being satisfied that you're on the best BNG for your location? Hopefully it's the nearest BNG to you in terms of distance. Mine certainly was at least until earlier 🙂
22-07-2022 12:27 PM - edited 22-07-2022 12:32 PM
Was downtime for this long something that you experienced? I had a quick scan through and you mentioned briefer downtime than this. Unless I missed something.
Update: CF report an incident involving a multiple circuit outage. I might be affected by this. All lights are green on the CF ONT, it's the red light flashing on the router that made me think it might just be related to VF.
22-07-2022 12:36 PM
@Gerry_Atric wrote:Was downtime for this long something that you experienced? I had a quick scan through and you mentioned briefer downtime than this. Unless I missed something.
Update: CF report an incident involving a multiple circuit outage. I might be affected by this. All lights are green on the CF ONT, it's the red light flashing on the router that made me think it might just be related to VF.
Yes I had downtime starting from 9pm one night lasting until 4am of the day after.
22-07-2022 12:37 PM
Also regarding the BNG I see myself being routed through Watford which if you look the map is very close to Coventry. The ping has been between 6 and 12. For some reason it's hung around 10-12 most of the time lately but it might drop down I think as they rollout their fixes throughout the country.
22-07-2022 12:48 PM
I'm surprised they don't have a BNG nearer to Coventry like Birmingham. They seem to have them in Scotland, North England and South England. Surely there's something in the Midlands!
After waiting over 40 minutes to get through, the wifi experts team confirmed there's a CityFibre related outage in my area which I think ties in with the CityFibre incident to do with multiple circuits - core network issue. I'll wait for them to resolve it, I'm thankful I have 4G backup up and running for the time being.
I just have to hope I don't return to the 'wrong' BNG when the service is restored!