We are aware of issues impacting access to some sites in the 193.195.141.0/24 subnet owing to routing issues with one of our upstream providers.
We are working on resolving these issues currently and will post a further update once more information is available.
There has been an intermittent issue with one of our upstream providers (Cogent) who have a corrupted / polluted route object for some of our IPv4 space
We have been working with them to resolve the issue today, however it has meant that connections into our network over IPv4 from certain ISPs has been seriously impacted.
IPv6 connections have continued to work without disruption
We are still working with Cogent and other upstreams to resolve the polluted record caused by another provider in our upstream making a change overnight which impacted our services, we’re also working to ensure that this won’t happen again.
I can only apologise for the disruption to service that this has caused.
At roughly 2 am, a rogue update to one of our Vodafone route objects caused BGP peers to drop routes to 193.195.141.0/24. We spotted this at approximately 4 am and raised the alarm. It took until 11 am for the upstream teams to confirm the issue, and by 2 pm, a fix had been implemented. We now need this to propagate across the internet.
Access to websites and email via IPv6 has remained unaffected during this issue.
We are working with Vodafone, Cogent and our peers to minimise the future impact of changes. It seems someone believed the route object was stale, deleted it and then found they were unable to re-create it – it took a while to find someone within Vodafone with sufficient permissions to update the route objects for that block.
The FXRM portal should have been accessible via IPv6; however, the AAAA record had been disabled during an earlier upgrade and had not yet been re-enabled, causing all traffic to default to IPv4. This AAAA record has now been reinstated.