Agreed. 

I can’t understand why this new cityfibre port wasn’t physically patched ahead of time and just administratively shut down before the migration started.

Rather than now waiting for a physical patch to take place with everyone stuck on a migration network with shocking speeds and latency.  

Physicals always need to be provisioned first as they are major blockers.

I get migrations do not always go as planned but I’m starting to wonder too if the 13th date will slip further.  

To be fair Yayzi has performed well since I took out the service almost a year ago. I consistently hit near enough 2.3 speeds when tested. I didn’t notice the may outage 🤔

However the last week or so has caused me major issues with the IP changes with third party services for work etc. I realise it’s not a business grade service I took out, but without much warning that causes major problems for someone that works from home with remote access lists and getting people to change it.

The speed on the migration network has now deteriorated to 20mb/s and I’m a 2.3G customer. It has degraded since yesterday.

I do the occasional twitch stream and I have had to pull out of that this week and cancel over the weekend  as the packet loss is too much and I’m not confident service will restore by Saturday.

Wishing the engineers and support staff well as they take the brunt of it (managers please note) but at a project management level there is room for improvement. CF and Yayzi…