Flightcontrol Outage History

Flightcontrol is up right now

Pingoru has recorded 195 incidents for Flightcontrol: 195 in the last 12 months and 75 in the last 90 days.

Source: status.flyio.net

195incidents recorded
195last 12 months
75last 90 days
3 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct13
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct5%
Pingoru began tracking Flightcontrol in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261379 of 720 (11%)
May 202629114 of 744 (15%)
June 202622100 of 720 (14%)
July 20261834 of 744 (5%)
August 20263334 of 744 (5%)
September 20262625 of 720 (3%)
October 20261330 of 577 (5%)

Incidents, newest first

Minor February 19, 2026 Investigating registry issues affecting deploys 2h 51m Customer Applications, Machines API, Deployments

Started Feb 19, 2026, 09:14 PM UTC· resolved Feb 20, 2026, 12:05 AM UTC

  1. investigating Feb 19, 2026, 09:14 PM UTC

    We are currently investigating this issue.

  2. identified Feb 19, 2026, 09:43 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 19, 2026, 09:49 PM UTC

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

  4. identified Feb 19, 2026, 10:24 PM UTC

    While we have seen some improvement from the previous fix, we are still seeing elevated rates of Registry connection issues. Users may continue to see slower machine creates and deploys due to slow image pulls. Deploys may succeed on a retry. We are continuing to work on restoring normal registry performance

  5. resolved Feb 20, 2026, 12:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 18, 2026 Control plane state delayed on some hosts possibly causing network or deployment disruption 22m Customer Applications, Machines API, Deployments, Corrosion

Started Feb 18, 2026, 04:22 PM UTC· resolved Feb 18, 2026, 04:44 PM UTC

  1. identified Feb 18, 2026, 04:22 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Feb 18, 2026, 04:23 PM UTC

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

  3. monitoring Feb 18, 2026, 04:28 PM UTC

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

  4. resolved Feb 18, 2026, 04:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 17, 2026 flyctl deploy timeouts 1h 18m Deployments

Started Feb 17, 2026, 01:06 PM UTC· resolved Feb 17, 2026, 02:24 PM UTC

  1. identified Feb 17, 2026, 01:06 PM UTC

    We’re investigating elevated 429 errors from flaps causing deployment timeouts. Affected deploys are failing with: ✖ Failed: error waiting for release_command machine XX to finish running: timeout reached waiting for machine's state to change Your machine never reached the state "destroyed".

  2. monitoring Feb 17, 2026, 01:42 PM UTC

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

  3. resolved Feb 17, 2026, 02:24 PM UTC

    Earlier today, an issue caused elevated rate limiting and some deployment timeouts. A fix is in place and deployments are back to normal.

Read the full incident report →

Major February 14, 2026 Degraded Managed Postgres Control Plane in ORD 2h 54m Management Plane - ORD

Started Feb 14, 2026, 11:33 AM UTC· resolved Feb 14, 2026, 02:27 PM UTC

  1. investigating Feb 14, 2026, 11:33 AM UTC

    We are currently investigating issues with the MPG control plane in ORD. A small number of clusters in the region may be seeing replication lag or PGBouncers connectivity issues at this time.

  2. identified Feb 14, 2026, 11:47 AM UTC

    The issue has been identified and we are working on a fix. The majority of MPG clusters in ORD continue to run normally, though some users may still see degraded replicas at this time. Some clusters in the region will have experienced a primary -> replica failover.

  3. identified Feb 14, 2026, 01:47 PM UTC

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

  4. monitoring Feb 14, 2026, 02:07 PM UTC

    A fix has been implemented and we are seeing full recovery of the control plane in ORD. With that recovery we are seeing impacted replicas catching up and clusters returning to normal health. We're continuing to monitor for full recovery.

  5. resolved Feb 14, 2026, 02:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026 Issues with deploying apps using Depot builders for new accounts 46m Deployments

Started Feb 11, 2026, 08:44 PM UTC· resolved Feb 11, 2026, 09:30 PM UTC

  1. investigating Feb 11, 2026, 08:44 PM UTC

    Some new Fly.io users may encounter an "upgrade your organization" error message when attempting to deploy apps for the first time. We're currently working with Depot to figure out what's causing the issue. In the meantime, you should be able to work around the issue by using Fly builders with `fly deploy --depot=false`.

  2. identified Feb 11, 2026, 08:57 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 11, 2026, 09:24 PM UTC

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

  4. resolved Feb 11, 2026, 09:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026 Creating new sprites is degraded 1h 15m Sprites

Started Feb 11, 2026, 06:07 AM UTC· resolved Feb 11, 2026, 07:22 AM UTC

  1. investigating Feb 11, 2026, 06:07 AM UTC

    Sprite creation generates an error that the sprite "is not assigned to compute." Eventually the sprite transitions from an unknown state to warm, so there is a delay before the sprite is usable.

  2. investigating Feb 11, 2026, 06:08 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 11, 2026, 06:09 AM UTC

    We are continuing to investigate this issue.

  4. identified Feb 11, 2026, 06:52 AM UTC

    We've identified the cause of the delay following creates and we're deploying a fix.

  5. monitoring Feb 11, 2026, 06:57 AM UTC

    Sprite creation appears to be back to normal operation now.

  6. resolved Feb 11, 2026, 07:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 10, 2026 Degraded MPG clusters in IAD 1h 43m Management Plane - IAD

Started Feb 10, 2026, 07:00 PM UTC· resolved Feb 10, 2026, 08:44 PM UTC

  1. investigating Feb 10, 2026, 07:00 PM UTC

    We're currently looking into an issue with MPG clusters in the IAD region.

  2. identified Feb 10, 2026, 07:15 PM UTC

    We've identified the issue - some MPG clusters in IAD should be seeing improvements, and we're working on rolling out a fix for the remaining impacted clusters.

  3. identified Feb 10, 2026, 07:53 PM UTC

    We've rolled out a fix for some additional impacted clusters, and we're continuing to work on the remaining clusters.

  4. monitoring Feb 10, 2026, 08:00 PM UTC

    We've rolled out a fix for the remaining impacted clusters, and we're now monitoring the results.

  5. resolved Feb 10, 2026, 08:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 9, 2026 Issue creating new Sprites in IAD 1h 8m

Started Feb 09, 2026, 08:29 PM UTC· resolved Feb 09, 2026, 09:38 PM UTC

  1. investigating Feb 09, 2026, 08:29 PM UTC

    We're currently looking into an issue that's preventing new Sprites from being created in IAD. Sprite creation from other regions are unaffected.

  2. identified Feb 09, 2026, 08:45 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 09, 2026, 09:19 PM UTC

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

  4. resolved Feb 09, 2026, 09:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 9, 2026 Degraded network in AMS 3h 38m AMS - Amsterdam, Netherlands, Management Plane - AMS

Started Feb 09, 2026, 07:17 AM UTC· resolved Feb 09, 2026, 10:55 AM UTC

  1. investigating Feb 09, 2026, 07:17 AM UTC

    One of our upstream providers is performing an emergency DC maintenance. You may see degraded connectivity on some of your apps in AMS. Most apps in AMS are not affected.

  2. identified Feb 09, 2026, 07:34 AM UTC

    One of our upstream providers is experiencing a major power issue in their AMS datacenter. Managed Postgres instances in AMS are experiencing an outage as our control plane for Managed Postgres is taken down by the incident.

  3. identified Feb 09, 2026, 07:42 AM UTC

    Affected hosts are starting to come back online. We are working on restoring affected MPG clusters.

  4. identified Feb 09, 2026, 08:58 AM UTC

    We are still working on restoring the MPG clusters. Most of them should be operational already.

  5. monitoring Feb 09, 2026, 09:47 AM UTC

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

  6. resolved Feb 09, 2026, 10:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 7, 2026 Machines API issues 1h 49m Machines API

Started Feb 07, 2026, 04:23 PM UTC· resolved Feb 07, 2026, 06:13 PM UTC

  1. investigating Feb 07, 2026, 04:23 PM UTC

    We are investigating widespread Machines API issues since 16:00 UTC. You may experience 5xx errors or higher latency at this time.

  2. identified Feb 07, 2026, 04:40 PM UTC

    The issue has been identified and we are seeing Machines API performance improve in most regions since ~16:20 UTC. Machines API calls in the SYD, NRT, SIN region may continue to see 5xx errors or higher latency at this time. We are continuing to work on restoring full API performance in all regions

  3. monitoring Feb 07, 2026, 05:17 PM UTC

    A fix has been implemented and we are seeing Machines API connectivity improve in APAC regions. We continue monitoring for full recovery.

  4. resolved Feb 07, 2026, 06:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 7, 2026 Private Networking and Certificate Resolution Issues in SYD 2h 53m Management Plane - SYD, SSL/TLS Certificate Provisioning, SYD - Sydney, Australia

Started Feb 07, 2026, 03:19 PM UTC· resolved Feb 07, 2026, 06:12 PM UTC

  1. investigating Feb 07, 2026, 03:19 PM UTC

    We are investigating communication issues between some SYD (Sydney, Australia) region hosts and our Certificate vault. Requests hitting SYD region edges may see issues resolving certificates at this time, especially for newly issued or not recently used certificates.

  2. investigating Feb 07, 2026, 03:21 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 07, 2026, 03:46 PM UTC

    Private Networking (6PN) is degraded in SYD region. Communication between Machines in SYD region and Machines in other regions may fail at this time. Newly created Machines in SYD may fail to sync to other regions (may not show up in Machines API List endpoint, or state may be incorrect). We are working with our upstream providers to resolve this issue.

  4. monitoring Feb 07, 2026, 04:24 PM UTC

    A fix has been implemented and we are seeing private networking / certificates in SYD improving. We are continuing to monitor for full recovery.

  5. resolved Feb 07, 2026, 06:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 5, 2026 Network issues on newly-created machines 9h 14m Customer Applications

Started Feb 05, 2026, 09:52 PM UTC· resolved Feb 06, 2026, 07:07 AM UTC

  1. identified Feb 05, 2026, 09:52 PM UTC

    Machines created after the delayed machine registration incident (https://status.flyio.net/incidents/3npj6935byt4) may have incomplete networking configurations and could be unable to receive traffic. We've identified the issue and are deploying code fixes as well as updating created machines. This affects a small number of machines on all our regions.

  2. monitoring Feb 06, 2026, 02:49 AM UTC

    We have successfully run a fix to re-sync our global and regional state stores in order to bring machines back to a healthy state, and we're monitoring the situation to confirm that there are no more issues.

  3. resolved Feb 06, 2026, 07:07 AM UTC

    This issue is now resolved.

Read the full incident report →