Flying Circus

All Systems Operational

About This Site

This is the global, public status page of the Flying Circus Internet Operations GmbH


Privacy Policy

Uptime over the past 90 days. View historical uptime.
RZOB (production) Operational
90 days ago
99.99 % uptime
Today
VM servers Operational
90 days ago
99.99 % uptime
Today
VM storage cluster Operational
90 days ago
99.99 % uptime
Today
VM backup Operational
90 days ago
100.0 % uptime
Today
AI API Operational
90 days ago
99.98 % uptime
Today
Network and Internet uplink Operational
90 days ago
99.96 % uptime
Today
Central services Operational
90 days ago
99.96 % uptime
Today
my.flyingcircus.io Operational
90 days ago
100.0 % uptime
Today
gitlab.flyingcircus.io Operational
90 days ago
100.0 % uptime
Today
Emergency Channels Operational
90 days ago
100.0 % uptime
Today
Hotline Operational
90 days ago
100.0 % uptime
Today
Support emails Operational
90 days ago
100.0 % uptime
Today
RZHAL (backup and development data center) Operational
90 days ago
99.98 % uptime
Today
VM servers Operational
90 days ago
99.99 % uptime
Today
VM storage cluster Operational
90 days ago
99.99 % uptime
Today
VM backup Operational
90 days ago
100.0 % uptime
Today
AI API Operational
90 days ago
100.0 % uptime
Today
Network and Internet uplink Operational
90 days ago
99.93 % uptime
Today
Related external services Operational
Bitbucket Git via HTTPS Operational
Bitbucket Mercurial via HTTPS Operational
Bitbucket SSH Operational
GitHub Operational
Fastly Europe (FRA) Operational
Fastly Europe (AMS) Operational
Python Infrastructure pypy.org Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Rolling out release 2026_022 Jun 8, 2026 21:00-23:00 CEST

Release 2026_022 is ready and will be rolled out during the specified timeframe.

See the Changelog for information about the specific changes and impact of the release.

Note: releases themselves do not cause downtimes. If a change within a release requires downtime then every VM that is affected will schedule a maintenance period according to your projects' preferences and notify you with specific details about the downtime.

Check the "Impact" section of the changelog (linked above) to see potential causes of downtimes in a release.
Posted on Jun 04, 2026 - 16:20 CEST
Jun 4, 2026

No incidents reported today.

Jun 3, 2026
NixOS CI/CD server ("Hydra") maintenance
Completed - The scheduled maintenance has been completed. Thank you for your patience.
Jun 3, 19:50 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 3, 19:00 CEST
Scheduled - We are working on our NixOS platform CI/CD server ("Hydra") that generates our Linux distribution and provides Nix channel tarballs. There will be at least one downtime of 10 minutes in this period which can affect system rebuilds ("fc-manage"). Deployments might fail because of this.

The performance of running applications is not affected and package downloads are handled by our S3 object storage independently of Hydra.
May 29, 15:21 CEST
Jun 2, 2026

No incidents reported.

Jun 1, 2026
Rolling out release 2026_020
Completed - The scheduled maintenance has been completed.
Jun 1, 23:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 21:00 CEST
Scheduled - Release 2026_020 is ready and will be rolled out during the specified timeframe.

See the Changelog for information about the specific changes and impact of the release.

Note: releases themselves do not cause downtimes. If a change within a release requires downtime then every VM that is affected will schedule a maintenance period according to your projects' preferences and notify you with specific details about the downtime.

Check the "Impact" section of the changelog (linked above) to see potential causes of downtimes in a release.
May 28, 16:05 CEST
May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026

No incidents reported.

May 28, 2026

No incidents reported.

May 27, 2026

No incidents reported.

May 26, 2026

No incidents reported.

May 25, 2026
Rolling out release 2026_019
Completed - The scheduled maintenance has been completed.
May 25, 23:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 25, 21:00 CEST
Scheduled - Release 2026_019 is ready and will be rolled out during the specified timeframe.

See the Changelog for information about the specific changes and impact of the release.

Note: releases themselves do not cause downtimes. If a change within a release requires downtime then every VM that is affected will schedule a maintenance period according to your projects' preferences and notify you with specific details about the downtime.

Check the "Impact" section of the changelog (linked above) to see potential causes of downtimes in a release.
May 21, 21:54 CEST
May 24, 2026

No incidents reported.

May 23, 2026

No incidents reported.

May 22, 2026

No incidents reported.

May 21, 2026
Storage outage after scheduled maintenance
Resolved - Between 00:15 and 00:26 our storage was unable to requests for a number of VMs hosted in the HDD class storage pool.

This happened after a regularly scheduled maintenance when two storage daemons did not cleanly reconnect to the cluster and caused requests to be stuck. We have seen this behaviour in the past but considered it resolved after having implemented workarounds. This has been proven untrue and we're now immediately disabling automatic maintenances until a further insights indicate a solution.
May 21, 00:00 CEST
← Incident History Powered by Atlassian Statuspage