Flightcontrol incident

High number of 5XX on the Machines API and dashboard

Critical Resolved View vendor source →

Flightcontrol experienced a critical incident on July 20, 2026 affecting Dashboard and Machines API, lasting 9h 59m. The incident has been resolved; the full update timeline is below.

Started
Jul 20, 2026, 07:10 AM UTC
Resolved
Jul 20, 2026, 05:09 PM UTC
Duration
9h 59m
Detected by Pingoru
Jul 20, 2026, 07:10 AM UTC

Affected components

DashboardMachines API

Update timeline

  1. investigating Jul 20, 2026, 07:10 AM UTC

    Existing machines are unaffected. We are investigating the issue.

  2. investigating Jul 20, 2026, 07:48 AM UTC

    We are continuing to investigate this issue.

  3. identified Jul 20, 2026, 07:51 AM UTC

    We've identified an internal service providing authentication to our Machines API has failed, our team is currently looking at our options for restoring this service. Existing Machines/Apps will continue to run as normal. Thank you for your patience.

  4. identified Jul 20, 2026, 07:52 AM UTC

    We've identified an internal service providing authentication to our Machines API has failed, our team is currently looking at our options for restoring this service. Existing Machines/Apps will continue to run as normal. Thank you for your patience.

  5. monitoring Jul 20, 2026, 08:02 AM UTC

    A fix has been implemented and we are monitoring the results.

  6. monitoring Jul 20, 2026, 09:14 AM UTC

    Some Managed Postgres v1 clusters are degraded. We are working on fixing them. Managed Postgres v2 is unaffected.

  7. monitoring Jul 20, 2026, 01:34 PM UTC

    We are still working on fixing degraded Managed Postgres clusters.

  8. resolved Jul 20, 2026, 05:09 PM UTC

    This incident has been resolved.