Flightcontrol incident

Slow API requests

Major Resolved View vendor source →
Started
Feb 27, 2026, 06:50 PM UTC
Resolved
Feb 27, 2026, 08:21 PM UTC
Duration
1h 31m
Detected by Pingoru
Feb 27, 2026, 06:50 PM UTC

Affected components

DashboardMachines APIDeploymentsRemote BuildsSprites

Update timeline

  1. investigating Feb 27, 2026, 06:50 PM UTC

    We are investigating increased in API request latency and timeouts with the main platform API. This is impacting multiple operations, including creating, querying or performing actions against machines, as well as platform level operations like adding payment methods.

  2. identified Feb 27, 2026, 06:52 PM UTC

    We have identified the cause of the increased latency and are working on a fix. The most common errors we are seeing is timeouts when users attempt to perform an action against a newly created app / machine resource. Those may timeout or fail with an `app|machine not found` error

  3. identified Feb 27, 2026, 06:53 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Feb 27, 2026, 06:59 PM UTC

    New Sprite creations are also timing out or failing at this time. We are continuing to work on a fix for this issue.

  5. identified Feb 27, 2026, 07:05 PM UTC

    We are currently seeing full API failures for requests to our Graphql API and elevated failures for the machines API. Direct calls to these apis may fail, along with many flyctl commands. We have identified the cause of the issue and are continuing to work on a fix. Existing running machines and apps should continue to be reachable, but creates, deploys, or other features relying on platform API calls will fail at this time.

  6. identified Feb 27, 2026, 07:23 PM UTC

    An initial fix has been deployed and we are seeing improvements in load and API performance. Some operations that rely on the Graphql API, such as new app creations and some deployments, will continue to fail at this time. We are continuing to work on restoring full availability.

  7. identified Feb 27, 2026, 07:41 PM UTC

    A second fix has been deployed and database load has returned to normal, resulting in API response times beginning to normalize. Most Machines API requests should succeed as normal, and deploys to existing apps should also work. We are working through a backlog of background jobs. New app / organization creations and other other operations that use these will continue to see increased latency or failures while we work thorough these. New MPG cluster and new Sprite creation continues to be impacted.

  8. monitoring Feb 27, 2026, 08:05 PM UTC

    API and platform operations have normalized. We are continuing to monitor to ensure full and stable recovery. Background jobs are almost fully caught up. Users may still see slightly slower requests creating new apps / orgs, but they should complete successfully. Sprite and MPG cluster creations are processing as normal.

  9. resolved Feb 27, 2026, 08:21 PM UTC

    This incident has been resolved. All platform and API operations are working normally.

Looking to track Flightcontrol downtime and outages?

Pingoru polls Flightcontrol's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Flightcontrol reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Flightcontrol alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Flightcontrol for free

5 free monitors · No credit card required