This is Birstall. WF17
Same here as well tbh
Not noticed it tbh, just got an alert.
I didn’t even notice, tbh. Started going bad at 6pm, I did wonder why YouTube was taking a while on initial buffer
My speeds were not impacted though
We’re just looking at this now guys!
Looks like a routing issue with our LONAP port, we’re rerouting traffic. Our apologies for that!
2 Likes
Was it an issue LONAP side or yours?
LONAP issue was causing that huge spike, back down to around 14ms on average which is still higher than I’d like to see.
14ms is perfectly fine, my ping is back down to 4-6ms.
You might think so but I don’t, not when I had a much lower ping before switching isp. XGS-PON has lower latency than GPON & it’s available on my postcode now but I’m still waiting to be switched to the 2.3 gig pro package, contacted support by email days ago & WhatsApp about how long it’s supposed to take but no reply as of yet.
Latency will not change based on XGS-PON technology - Your actual address isn’t showing up as XGS-PON, so its been sent to the CityFibre data team, just waiting for them to get back to us 
Weird when your checker shows this upon checking my postcode, city fibre checker shows 2.3Gbps speeds as available also. When I signed up last month the 2 gig pro package was listed & not the 2.5 gig pro.
I’m assuming your checking another address on your street? Like I said it’s your specific address that isn’t showing up as XGS-PON yet (its with the CityFibre data team)
yeah can’t check mine as it just says I’m already connected to yayzi, literally every other house number on my postcode shows 2.5 gig pro available.
In my experience, CityFibre only exclude single properties once they’re aware of an order that can’t be completed. This will be why the rest of your street shows as having XGS-PON.
For years, my flat was unavailable to the CityFibre network whereas every other flat (that I checked) showed as connected.
One property being unable to connect to XGS-PON when every other property on the same postcode can makes no sense to me although this is City fibre so who knows, but I think it’s either some weird database error or it’s completely wrong & my postcode hasn’t been upgraded yet.
Interesting.
My pings returned to normal around 21:30. However, I did get another ‘high latency’ warning this morning around 8:00 but this was a very brief and minor spike.
This whole LONAP thing though. A lot of us have been experiencing these same issues, although to a much lesser degree, on a nightly basis - seems to always between around 18:30-21:30 or thereabouts.
Is this the same issue then, or something else? i.e., now the routing has changed, will we see no spikes this evening?
Cheers.
If it’s due to congestion then it’ll keep happening but I’ve just seen the post about network migration happening over the next couple of weeks, lets see what improvements that brings to latency & congestion
Huge improvements based on the testing we’ve done, latency has over halved - adding the Manchester peering helps too 
- We’ve built this from scratch, so we’ve taken a lot of feedback from customers on here
3 Likes
And ridiculous amount of money…
1 Like