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_023 Jun 15, 2026 21:00-23:00 CEST

Release 2026_023 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 11, 2026 - 17:10 CEST
Jun 15, 2026
Ceph Storage Cluster Upgrade in WHQ (backup DC)
Completed - The scheduled maintenance has been completed.
Jun 15, 11:30 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 15, 08:30 CEST
Scheduled - We will upgrade our Ceph storage cluster in our backup data center (location WHQ). The upgrade is designed as a no-downtime operation, but might increase load on the storage backend during that period.
The qemu KVM cluster will be updated as well to match the new storage.

Our engineers will be monitoring and guiding the upgrade closely, ensuring timely responses to unexpected events.
Jun 12, 20:51 CEST
Jun 14, 2026

No incidents reported.

Jun 13, 2026

No incidents reported.

Jun 12, 2026

No incidents reported.

Jun 11, 2026

No incidents reported.

Jun 10, 2026

No incidents reported.

Jun 9, 2026

No incidents reported.

Jun 8, 2026
Rolling out release 2026_022
Completed - The scheduled maintenance has been completed.
Jun 8, 23:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 8, 21:00 CEST
Scheduled - 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.
Jun 4, 16:20 CEST
Jun 7, 2026

No incidents reported.

Jun 6, 2026

No incidents reported.

Jun 5, 2026

No incidents reported.

Jun 4, 2026

No incidents reported.

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
← Incident History Powered by Atlassian Statuspage