Have you done a tracert to check which gateway you are connecting to? They changed my FTTC to connect to Manchester (even though my head exchange is in Dorset) and I lost IPv6 (and latency doubled). They changed me back to London and IPv6 was restored.

Yes the speed is poor on a variety of PoPs. Both Manchester and London. I did notice that the Manchester one doubled my first hop latency, despite being very close to Manchester geographically.

Zen called me and we ran through a thorough set of troubleshooting steps to no avail. Then shortly afterwards a fault manager called me and said that I'd be getting an Openreach engineer visit soon. I doubt they'll find anything physically wrong here but you never know.

Thanks to Andrew on here for getting the ball rolling though.

In reply to a post by FakeJake:

I'd be getting an Openreach engineer visit soon.

Did they try temporarily reversing the migration as that would seem the most logical next step and is probably step 1 in the dummies guide to fault finding.

In reply to a post by FakeJake:

.
I've also noticed that my IPv6 is gone... Hopefully this can be easily and quickly fixed

That apparently always happens with a GEA migration with Zen.
You just need to fill in the IPV6 form again or send them a quick message and they will enable it again.

So why don't they simply check and fix it themselves? Aren't they supposed to be a class act?

In reply to a post by pluralist:

So why don't they simply check and fix it themselves? Aren't they supposed to be a class act?

They used to be a class act, but I'm not so sure that they are any longer. They seem to want to change from a niche ISP to a mass market one.

In reply to a post by dect:

Hi ajays

Out of interest do the Zen migrations team notify customers when this type of work is going to happen and what measures do they put in place to test and ensure customers are not negatively affected by their changes?

I'll take from your silence that Zen neither notify their customers of this service affecting change nor do any testing to ensure their customers are not negatively impacted.

They don't. Mine was migrated on the 7th it seems (you'll have an entry in the orders section of the zen portal) and I was never notified. My bqm graph though shows the latency doubled a few days later after the usual gateway change. I'm honestly thinking of leaving zen with all this rubbish over their manchester/london gateways.

How can this be considered normal on an FTTP 900 package?

https://www.thinkbroadband.com/broadband/monitoring/...

This was today:

Speedtest: https://www.speedtest.net/result/12971030032.png
Traceroute:

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 218 ms 217 ms 222 ms lo0-0.bng3.wh-man.zen.net.uk [51.148.77.130]
3 240 ms 239 ms 252 ms lag-7.p2.wh-man.zen.net.uk [51.148.73.14]
4 266 ms 275 ms 309 ms lag-3.p1.thn-lon.zen.net.uk [51.148.73.136]
5 316 ms 314 ms 321 ms lag-1.br1.thn-lon.zen.net.uk [51.148.73.153]
6 373 ms 311 ms 268 ms 72.14.223.28
7 * 23 ms 22 ms 209.85.249.149
8 21 ms 22 ms 22 ms 142.251.54.31
9 20 ms 20 ms 20 ms dns.google [8.8.8.8]

Speedtest: https://www.speedtest.net/result/12971085484.png
Traceroute:

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 11 ms 8 ms lo0-0.bng2.ixn-lon.zen.net.uk [51.148.77.129]
3 9 ms 8 ms 8 ms lag-4.p1.ixn-lon.zen.net.uk [51.148.73.89]
4 8 ms 8 ms 8 ms lag-2.p1.thn-lon.zen.net.uk [51.148.73.132]
5 8 ms 7 ms 8 ms lag-1.br1.thn-lon.zen.net.uk [51.148.73.153]
6 9 ms 8 ms 8 ms 72.14.223.28
7 10 ms 10 ms 10 ms 209.85.249.149
8 7 ms 8 ms 8 ms 142.251.54.31
9 8 ms 7 ms 8 ms dns.google [8.8.8.8]

A difference of 20ms -> 8ms

Edited by zebb_edi (Thu 31-Mar-22 14:20:59)

This looks fine to me. I currently achieve about 40mbps down, 110mbps up.

At least my uploads are ok!

The GEA migration seems ok for me. It's their gateway disparity that is daft.