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 572 (5%)

Incidents, newest first

Major June 17, 2026 Network Issues in SIN 1h 33m SIN - Singapore

Started Jun 17, 2026, 03:21 AM UTC· resolved Jun 17, 2026, 04:55 AM UTC

  1. investigating Jun 17, 2026, 03:21 AM UTC

    We are currently investigating network connectivity issues in the SIN region. Hosted apps may be unavailable.

  2. identified Jun 17, 2026, 03:47 AM UTC

    Some machines in SIN are unreachable. A few Managed Postgres clusters may fail to fail-over or update. We are in the process of fixing this with our upstream provider.

  3. identified Jun 17, 2026, 04:22 AM UTC

    We are seeing recovery of network connectivity between SIN and most destinations. We're continuing to work with our upstream provider to resolve the remaining issues.

  4. monitoring Jun 17, 2026, 04:38 AM UTC

    Network connectivity in SIN has been fully restored. We're continuing to monitor.

  5. resolved Jun 17, 2026, 04:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 15, 2026 Macaroon Auth + Machines API Issues 1h 10m Management Plane - ORD, Dashboard, Management Plane - IAD, Machines API and 12 more

Started Jun 15, 2026, 03:30 PM UTC· resolved Jun 15, 2026, 04:41 PM UTC

  1. investigating Jun 15, 2026, 03:03 PM UTC

    We are investigating issues with Macaroon based authentication. This is impacting parts of the Machines API, Fly.io Dashboard, some flyctl operations and other platform features that rely on this.

  2. identified Jun 15, 2026, 03:13 PM UTC

    We are continuing to address this issue. Platform authentication with macaroon based tokens is currently failing. Platform features that authenticate with macaroons including Machines API operations, Dashboard logins, some flyctl commands, fly-metrics.net Grafana, and deployments are failing at this time. Existing, running customer applications and machines remain reachable and running. We will provide another update within 15 minutes

  3. identified Jun 15, 2026, 03:30 PM UTC

    We have identified the cause of the issue and are working on deploying a fix. Impacted features remain unavailable or degraded at this time. Already running customer applications/machines remain available. MPG clusters remain generally reachable and healthy, however new clusters cannot be provisioned and failovers may not complete. We will provide another update within 15 minutes.

  4. identified Jun 15, 2026, 03:41 PM UTC

    An initial fix has been deployed and we are starting to see platform features recover. Users may still see degraded performance and intermittent failures at this time. We are continuing to address the issue to ensure a full stable recovery.

  5. identified Jun 15, 2026, 03:57 PM UTC

    We continue to seeing degraded performance and increased errors with the Machines API and other platform features at this time. We are continuing to work on fully restoring service.

  6. identified Jun 15, 2026, 04:00 PM UTC

    We are seeing elevated cluster errors with Managed Postgres clusters as the MPG control plane recovers from the API outage. MPG Users may see elevated rates of failing or slow connections, as well as increased primary/replica failovers. The managed postgres team is addressing any degraded clusters. We will provide a further update within 15m.

  7. identified Jun 15, 2026, 04:15 PM UTC

    We have deployed another change and are seeing wider improvements in platform stability across all regions. Performance is trending to normal, though users may still see some degradation at this time. We are continuing to closely monitor to ensure full, stable recovery. We will provide another update in 15m.

  8. monitoring Jun 15, 2026, 04:15 PM UTC

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

  9. resolved Jun 15, 2026, 04:41 PM UTC

    This incident has been resolved and we are seeing all platform functions operate normally.

Read the full incident report →

Notice June 15, 2026 MPG cluster provisioning is broken 18m

Started Jun 15, 2026, 06:20 AM UTC· resolved Jun 15, 2026, 06:39 AM UTC

  1. investigating Jun 15, 2026, 06:20 AM UTC

    New MPG cluster provisioning is broken. Existing MPG clusters are not affected. Newly created organizations may see errors while SSHing into their machines. We are investigating the issue.

  2. resolved Jun 15, 2026, 06:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2026 Elevated Sprites error rates in SIN 1h 54m Sprites

Started Jun 12, 2026, 02:35 AM UTC· resolved Jun 12, 2026, 04:30 AM UTC

  1. investigating Jun 12, 2026, 02:35 AM UTC

    We are investigating elevated 500 / internal server error rates with Sprites in the SIN region. Users may see increased errors when accessing sprites located in this region, or for requests to the Sprites API originating from SIN

  2. monitoring Jun 12, 2026, 03:24 AM UTC

    A fix has been implemented and we are seeing error rates for sprites in SIN normalize. We are continuing to monitor to ensure full recovery.

  3. resolved Jun 12, 2026, 04:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2026 Increased network latency in North America 9h 56m Management Plane - ORD, ORD - Chicago, Illinois (US)

Started Jun 11, 2026, 01:16 AM UTC· resolved Jun 11, 2026, 11:12 AM UTC

  1. investigating Jun 11, 2026, 01:16 AM UTC

    We are investigating elevated network instability across some hosts in ORD. Apps and managed postgres clusters on impacted hosts may see elevated latency or networking errors at this time.

  2. monitoring Jun 11, 2026, 01:59 AM UTC

    Managed Postgres in ORD has returned to normal operation. We continue to see slightly elevated latencies and loss over transits in North America. We are working with our upstream network providers to improve performance.

  3. monitoring Jun 11, 2026, 03:30 AM UTC

    Impacted NA backbones have been sidestepped where possible, and we're continuing to monitor network health.

  4. monitoring Jun 11, 2026, 05:24 AM UTC

    The network between our regions has been performing well for the majority of traffic. We're still continuing to monitor a few impacted routes in North America that may be seeing elevated latency and packet loss.

  5. identified Jun 11, 2026, 07:58 AM UTC

    We are seeing a recurrence of elevated latency across some hosts in ORD impacting the MPG control plane and a subset of clusters there. We are working to address this.

  6. identified Jun 11, 2026, 09:35 AM UTC

    We are working with our upstream network provider to address periodic loss of connectivity over transit in ord

  7. monitoring Jun 11, 2026, 10:09 AM UTC

    Our upstream paths have been fixed. We are monitoring the results.

  8. resolved Jun 11, 2026, 02:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 10, 2026 Ingress Traffic issues in GRU 13m GRU - Sao Paulo, Brazil

Started Jun 10, 2026, 07:39 PM UTC· resolved Jun 10, 2026, 07:52 PM UTC

  1. identified Jun 10, 2026, 07:39 PM UTC

    Some of our edge nodes in GRU has suffered an error that crashed some of the critical services. We're currently working to bring them back online. Some traffic entering through GRU (i.e. users connecting from around GRU) may be temporarily affected: connections may see increased latency or be occasionally dropped.

  2. resolved Jun 10, 2026, 07:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 9, 2026 Emergency maintenance of Petsem causing some control plane errors 22m Machines API

Started Jun 09, 2026, 06:20 PM UTC· resolved Jun 09, 2026, 06:42 PM UTC

  1. identified Jun 09, 2026, 06:20 PM UTC

    We're performing an emergency maintenance on Petsem, our secrets management service. Some control plane write operations may temporarily fail, for example, creating new apps or secrets. Existing apps and machines should keep functioning without issues.

  2. monitoring Jun 09, 2026, 06:28 PM UTC

    The maintenance has been completed and control plane functions should recover to normal. We're monitoring for any further complications.

  3. resolved Jun 09, 2026, 06:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 9, 2026 Managed Postgres Control Plane Issues in IAD 1h 17m Management Plane - IAD

Started Jun 09, 2026, 02:57 PM UTC· resolved Jun 09, 2026, 04:15 PM UTC

  1. investigating Jun 09, 2026, 02:57 PM UTC

    We are investigating MPG control plane instability in a subset of the IAD region. A small number of clusters in the region may have seen unexpected failovers or connection issues over the past 30m.

  2. identified Jun 09, 2026, 03:06 PM UTC

    We are continuing to address this issue. Some clusters in IAD are unavailable at this time, some users may have seen unexpected cluter restarts. We are working on restoring normal performance for all clusters in IAD

  3. monitoring Jun 09, 2026, 03:19 PM UTC

    An initial fix has been implemented and connectivity to all impacted clusters has been restored. We are continuing to monitor to ensure stable recovery.

  4. resolved Jun 09, 2026, 09:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 9, 2026 egress ips are broken in ORD 45m ORD - Chicago, Illinois (US)

Started Jun 09, 2026, 09:16 AM UTC· resolved Jun 09, 2026, 10:01 AM UTC

  1. investigating Jun 09, 2026, 09:16 AM UTC

    Egress ips are broken in most of ORD, we are currently investigating this issue

  2. monitoring Jun 09, 2026, 09:37 AM UTC

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

  3. resolved Jun 09, 2026, 10:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 8, 2026 Capacity issues in ARN region 1h 58m ARN - Stockholm, Sweden

Started Jun 08, 2026, 10:31 AM UTC· resolved Jun 08, 2026, 12:30 PM UTC

  1. investigating Jun 08, 2026, 10:31 AM UTC

    The ARN region is low on available host capacity. Creating new machines, or starting currently stopped/suspended machines, may fail at this time. We are working on provisioning new host capacity in the region. Please consider using nearby regions if possible.

  2. resolved Jun 08, 2026, 12:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 4, 2026 Consul cluster degradation 3h 19m

Started Jun 04, 2026, 01:44 PM UTC· resolved Jun 04, 2026, 05:03 PM UTC

  1. identified Jun 04, 2026, 01:44 PM UTC

    One of our Consul clusters is in degraded state due to a failed node. This can cause issues with LiteFS primary node selection, Unmanaged Postgres (14.x and older *only*), and creation of new Unmanaged Postgres clusters. Impact is limited to these legacy products and does not affect deployments, running Fly applications in general, or Managed Postgres clusters.

  2. monitoring Jun 04, 2026, 04:02 PM UTC

    We have restored the degraded Consul cluster and are monitoring for stability. All affected functionality should now be working correctly: Unmanaged Postgres and LiteFS with dynamic leases.

  3. resolved Jun 04, 2026, 05:03 PM UTC

    We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.

Read the full incident report →

Minor June 1, 2026 Issues with flyctl ssh console and Machines OIDC 10m Machines API

Started Jun 01, 2026, 06:33 PM UTC· resolved Jun 01, 2026, 06:43 PM UTC

  1. investigating Jun 01, 2026, 06:33 PM UTC

    We're currently investigating an issue affecting flyctl ssh console functionality and machines' OIDC tokens.

  2. monitoring Jun 01, 2026, 06:35 PM UTC

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

  3. resolved Jun 01, 2026, 06:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 31, 2026 IPv6 outage for some machines in ORD 4h 17m ORD - Chicago, Illinois (US)

Started May 31, 2026, 06:34 AM UTC· resolved May 31, 2026, 10:52 AM UTC

  1. investigating May 31, 2026, 06:34 AM UTC

    We're working with our upstream providers to investigate an IPv6 networking failure in ORD.

  2. monitoring May 31, 2026, 07:03 AM UTC

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

  3. resolved May 31, 2026, 10:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 30, 2026 Private networking issues in SYD 8m SYD - Sydney, Australia

Started May 30, 2026, 01:29 PM UTC· resolved May 30, 2026, 01:37 PM UTC

  1. identified May 30, 2026, 01:29 PM UTC

    Due to an upstream provider issue, Private Networking (6PN) is currently 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). Additionally, TLS certificate resolution and Machines API authentication may currently be degraded in the SYD region. We are working with our upstream providers to resolve this issue.

  2. monitoring May 30, 2026, 01:32 PM UTC

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

  3. resolved May 30, 2026, 01:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 30, 2026 Elevated deployment errors 1h 38m Deployments

Started May 30, 2026, 02:42 AM UTC· resolved May 30, 2026, 04:21 AM UTC

  1. investigating May 30, 2026, 02:42 AM UTC

    We're investigating an increase in deployment errors affecting some users. At this time, creating or updating Machines may erroneously fail with the message: "We require your billing information, please add it at https://fly.io/dashboard//billing".

  2. identified May 30, 2026, 03:13 AM UTC

    We identified the issue and are working on a fix.

  3. monitoring May 30, 2026, 03:37 AM UTC

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

  4. resolved May 30, 2026, 04:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026 Networking issues in ORD 36m ORD - Chicago, Illinois (US)

Started May 29, 2026, 07:09 PM UTC· resolved May 29, 2026, 07:45 PM UTC

  1. identified May 29, 2026, 07:09 PM UTC

    We are aware of increased latency and connection drops for clients located near Chicago (ORD) and are currently working on a fix.

  2. monitoring May 29, 2026, 07:21 PM UTC

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

  3. resolved May 29, 2026, 07:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026 Increased latency in SJC 1h 58m LAX - Los Angeles, California (US), SJC - San Jose, California (US)

Started May 28, 2026, 09:08 PM UTC· resolved May 28, 2026, 11:07 PM UTC

  1. investigating May 28, 2026, 09:08 PM UTC

    We are currently investigating increased latency in SJC.

  2. monitoring May 28, 2026, 09:56 PM UTC

    We have implemented a mitigation for the issue and are monitoring for stability. This issue happened on the edge hosts in SJC, which means that any traffic near/around SJC would have been affected during the incident. We will provide a more detailed write-up on our Infra Log (https://fly.io/infra-log/) later once we have a better picture of the entire incident.

  3. identified May 28, 2026, 10:25 PM UTC

    We're still seeing connection issues originating from SJC/LAX/West Coast US and are still investigating.

  4. monitoring May 28, 2026, 10:33 PM UTC

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

  5. monitoring May 28, 2026, 10:34 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved May 28, 2026, 11:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2026 Elevated GraphQL API Latency 45m Dashboard

Started May 27, 2026, 03:50 AM UTC· resolved May 27, 2026, 04:36 AM UTC

  1. investigating May 27, 2026, 03:50 AM UTC

    We are investigating elevated API Latency. Users may see delays or errors creating apps, as well as on some dashboard pages.

  2. monitoring May 27, 2026, 04:07 AM UTC

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

  3. resolved May 27, 2026, 04:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 26, 2026 Capacity issues in EWR region 1h 32m EWR - Secaucus, NJ (US)

Started May 26, 2026, 05:34 PM UTC· resolved May 26, 2026, 07:06 PM UTC

  1. identified May 26, 2026, 05:34 PM UTC

    The EWR region is low on available host capacity. Creating new machines, or starting currently stopped/suspended machines, may fail at this time. We are working on provisioning new host capacity in the region. Please consider using nearby regions such as ord if possible.

  2. resolved May 26, 2026, 07:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 23, 2026 Networking performance degraded in BOM and SJC 1d 22h BOM - Mumbai, India, SJC - San Jose, California (US)

Started May 23, 2026, 01:00 AM UTC· resolved May 24, 2026, 11:07 PM UTC

  1. investigating May 23, 2026, 01:01 AM UTC

    We're currently looking into this issue.

  2. monitoring May 23, 2026, 02:14 AM UTC

    Network performance has been restored and we're continuing to monitor.

  3. resolved May 24, 2026, 11:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 22, 2026 IPv6 outage for some machines in SIN 2h 12m SIN - Singapore

Started May 22, 2026, 01:32 PM UTC· resolved May 22, 2026, 03:44 PM UTC

  1. investigating May 22, 2026, 01:32 PM UTC

    We are currently investigating this issue.

  2. investigating May 22, 2026, 01:34 PM UTC

    We are continuing to investigate this issue.

  3. monitoring May 22, 2026, 01:57 PM UTC

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

  4. resolved May 22, 2026, 03:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 21, 2026 Network issues in SIN region 1h 28m Management Plane - SIN, SIN - Singapore

Started May 21, 2026, 06:30 PM UTC· resolved May 21, 2026, 07:59 PM UTC

  1. investigating May 21, 2026, 06:30 PM UTC

    We are investigating network issues in the Singapore region. Apps may experience higher latency or be unreachable at this time. Some Managed Postgres clusters may be unreachable.

  2. monitoring May 21, 2026, 06:45 PM UTC

    Our upstream provider has implemented a fix and all apps and Managed Postgres clusters are now reachable. For the time being, ingress traffic is being re-routed to other regions, so users around the Singapore area may experience higher latency.

  3. resolved May 21, 2026, 07:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026 Networking issues in SIN 16h 9m Management Plane - SIN, SIN - Singapore

Started May 20, 2026, 08:06 AM UTC· resolved May 21, 2026, 12:15 AM UTC

  1. investigating May 20, 2026, 08:06 AM UTC

    Machines may see high packet loss. Some MPGs are unable to connect to their config store and may be unreachable right now.

  2. identified May 20, 2026, 08:23 AM UTC

    One of our upstreams is experiencing high packet loss and latency. We are actively working with them.

  3. identified May 20, 2026, 08:59 AM UTC

    All MPGs in SIN are reachable again. We are seeing high latency to the affected provider. This may affect a subset of machines hosted in SIN.

  4. resolved May 21, 2026, 12:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026 Networking issues with egress IP addresses in SYD 2h 59m SYD - Sydney, Australia

Started May 20, 2026, 05:05 AM UTC· resolved May 20, 2026, 08:05 AM UTC

  1. investigating May 20, 2026, 05:05 AM UTC

    We are currently investigating an issue affecting networking for new apps with assigned egress IP addresses in our SYD region

  2. identified May 20, 2026, 05:57 AM UTC

    We've identified the issue and are working on a fix.

  3. monitoring May 20, 2026, 07:11 AM UTC

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

  4. resolved May 20, 2026, 08:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 19, 2026 Issues with the Fly.io dashboard 1h 17m Dashboard, Deployments

Started May 19, 2026, 11:19 PM UTC· resolved May 20, 2026, 12:36 AM UTC

  1. investigating May 19, 2026, 11:19 PM UTC

    We're currently investigating an issue where the Fly.io dashboard is failing to load in some cases.

  2. identified May 19, 2026, 11:34 PM UTC

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

  3. identified May 19, 2026, 11:50 PM UTC

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

  4. monitoring May 20, 2026, 12:26 AM UTC

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

  5. resolved May 20, 2026, 12:36 AM UTC

    This incident has been resolved.

Read the full incident report →