The upstream provider has acknowledged another technical defect on the line and has fixed it.
We're waiting for a more detailed RFO and will use that to decide on steps for future reliability improvements on our backup DC uplink.
Posted Nov 13, 2026 - 16:19 CET
Update
Customer-specified service checks have been re-enabled.
Posted Nov 13, 2026 - 13:41 CET
Update
As there was still no contact to our upstream network provider, we are leaving Customer-specified service checks (as shown on https://my.flyingcircus.io) disabled for now to avoid false alerts. All other services remain available for now, consider the overall situation still unstable though.
Posted Nov 13, 2026 - 12:50 CET
Monitoring
The network link came back online, all affected services are available again. The upstream provider has not responded yet, the reason for outage is still unclear.
Posted Nov 13, 2026 - 12:41 CET
Update
These are the central services affected by the network failure:
* Our emergency hotline (partial, backup number still available) * Emergency emails * Customer-specified service checks (as shown on https://my.flyingcircus.io) * Our Matrix chat * gitlab.flyingcircus.io (which may affect automated deployments) * hydra.flyingcircus.io (which may affect automated deployments and system updates using "fc-manage")
Posted Nov 13, 2026 - 12:25 CET
Update
We suspect that today's upstream provider repair was not effective and that the intermittent outages from the last days have now lead to a major impact. We have reached out and are waiting for feedback from their service team.
Posted Nov 13, 2026 - 12:25 CET
Investigating
Our backup data center RZHAL is currently offline. Production workloads running in our main data center RZOB are not affected, but monitoring and alerting are affected.
Posted Nov 13, 2026 - 12:24 CET
This incident affected: Emergency Channels (Hotline, Support emails), Central services, gitlab.flyingcircus.io, and RZHAL (backup and development data center) (Network and Internet uplink).