Ping/Latency way higher Gigafast 900

[htyaH]

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?

[htyaH]

I wonder if a VPN could affect how routing occurs? I'm gonna try to give that a try.

[htyaH]

I've been running tests seeing what kind of IP's I've been getting, using a third party router I can disable/re-enable the WAN port quickly and seeing the IP changes it gives me a select number of IP's mainly from Scotland, some Ireland, and one was Birmingham.

[Jayach]

You can do it in the Vodafone router as well.

[htyaH]

Okay, called in again and spoke to them. Got someone nice who managed to get my problem in front of the senior engineers. Supposedly City Fibre's upgrading their servers and they've placed people on a backup BNG. They're gonna get back to me about when the upgrade will complete and I'll be placed back on the 'main' BNG, (BNG is what determines our routing). So it's not permanent, just a matter of time.

[htyaH]

Just got an update @Gerry_Atric, supposedly we should be back on the main BGN by Monday

[Gerry_Atric]

That's great, thanks for keeping us all informed. It's really appreciated!

Although I am confused as to it being a CityFibre related issue as a fellow member here is served via Openreach and has exactly the same issue - which is why some of us believed it's purely to do with VF.

In any case, thanks again, looking forward to normal service resuming on Monday!

I just wished they had proactively communicated this with us in the first place. Communications to end users must improve. 

[Ripshod]

I smell something more akin to a farmyard. How would cf fix this for me? 

[Gerry_Atric]

---

@Ripshod wrote:

I smell something more akin to a farmyard. How would cf fix this for me? 

---

This is when I'm going to make light of the situation and come up with some theories.

Maybe CityFibre are secretly a subsidiary of Openreach and in fact it's an Openreach problem.

Or perhaps the person who messed it up in VF is trying to cover their rear end by blaming CityFibre in order to protect themselves from being fired for incompetency.

Or are CityFibre and Openreach having a secret affair and actually having many cosy moments together like sharing infrastructure, staff and have jointly cocked it all up but CityFibre are taking one for the team to protect Openreach?

Or perhaps Openreach are secretly farming it all out to CityFibre?

But yeah, smells worse than the local farmyard here. I still put my money on it being a VF problem! 

[Ripshod]

Post of the month right there. Splitting my sides....... 

[Amanda]

Thanks for keeping the thread updated @htyaH 🙂 it sounds like you've been given more information than we have! 

I hadn't heard anything when I logged back on this morning, so I've chased it up again and we're still waiting an update - the team that flag up these type of issues has said they'd expect to know more on Monday. 
It may mean then from the updates you've had, that the service may be back to normal before they know much more. 

You're right about the whole communication of this being less than perfect - I've raised this too and had a chat to the team about it, as there needs to be better way of both us and our customers getting this type of information.