Fern Trading-backed UK ISP Giganet (Cuckoo) appears to have been suffering from a “mass service outage” over the past 12-24 hours which, judging by feedback from customers across the UK, has resulted in a variety of sporadic connectivity problems since around 3pm yesterday afternoon.
Firstly, credit where credit is due, because Giganet – unlike the biggest ISPs in this market – has done a reasonable job of keeping their service status page updated throughout the situation. Initially the provider reported that only users with Legacy (ADSL2+), SuperBOLT (FTTC), UltraBOLT (G.Fast) and UltraBEAM (FTTP) services were affected (i.e. Openreach), but we’ve also had reports of problems from those on their CityFibre platform too (this also impacted other ISPs on the same network).
Customers have generally been reporting several periods – lasting anything from a few minutes to a few hours – of total internet connectivity loss during yesterday afternoon and evening. According to Giganet, this appears to have been caused by a “power failure” at one of their partner’s carrier networks (none are named). The good news is that “all remaining services were restored at 4:30am” this morning, but we note that they’ve also been having some issues with one of their authentication (radius) servers for several days.
Advertisement
However, it should be said that some of Giganet’s customers have just reported another service interruption that appears to have occurred at around 9am this morning, although at the time of writing it’s unclear whether this is a national or more localised problem (the issue has not yet been noted on their service status page).
“Our partner carrier confirmed that all remaining services were restored at 4:30am. We thank you for your patience and we sincerely apologise for the inconvenience caused during this time. We are continuing to monitor for any further issues,” said the latest service update. Take note that major outages at Giganet are generally very rare.
UPDATE 15th May 2023
We’ve had an update from Giganet.
Advertisement
A Spokesperson for Giganet said:
“Around 35% of our customer base were affected by a short outage caused on Wednesday 9 May, and Thursday 10 May, with a small number of customers affected for a longer duration. Customers accessing Giganet’s own network were completely unaffected during this period.
While our Status Page cited reported outages with our ADSL and FTTC customer base, this was in error and the issues were isolated to those on the affected network. We will now be updating our Status Page to ensure it is accurate going forward. We are actively working with our carrier on their post incident review process and can confirm all services have now been restored. We would like to thank our customers for their patience during this process.”
Looks like a CityFibre outage. No One also reported the same thing and provided regular updates.
http://status.as49375.net/incident/347834
As Giganet themselves said, it impacted their Openreach services too (Cityfibre don’t do ADSL and FTTC etc.). Likewise, it was much more widespread than Leeds and York, impacting locations across the country. Not everybody will have noticed, though.
If you follow the updates on the status page for No One and Giganet, the timescales, causes and remediation steps line up perfectly. (E.g original engineer for both events turning up at exactly 19:00, then both pages need another engineer who is turning up at exactly 19:45)
Either it was a massive coincidence that two identical outages started at the same time, had the same cause and remediated at the same time, or they’re the same event.
Cityfibre via their Entanet acquisition do supply BT Wholesale based ADSL, FTTC and FTTP.
No issues on Giganet’s own network in Hampshire. Been humming like a dream since it went live 🙂 MKM
My Vodafone cityfibre cut out for about an hr yesterday at around 3-4pm in suffolk
> Looks like a CityFibre outage. No One also reported the same thing and provided regular updates.
Assuming this is related, AAISP had it covered
https://aastatus.net/42538
It was a CityFibre problem that multiple ISPs reported on.
I’m with Giganet on Cityfibre, use the internet pretty much 24/7 and had 100% uptime for at least the last week, so it wasn’t entirely a universal problem.