Flightcontrol Outage History

Flightcontrol is up right now

Flightcontrol had 151 outages in the last 2 years totaling 26h 9m of downtime — averaging 6.2 incidents per month.

There were 151 Flightcontrol outages since February 5, 2026 totaling 26h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.flyio.net

Critical October 3, 2026

Partial outage in AMS

Detected by Pingoru
Oct 03, 2026, 08:01 AM UTC
Resolved
Oct 03, 2026, 08:57 AM UTC
Duration
56m
Timeline · 5 updates
  1. identified Oct 03, 2026, 08:01 AM UTC

    Some of our hosts are offline in AMS. Control plane for Managed Postgres v1 and v2 in AMS is unavailable as a result of this. MPG clusters should remain online but any control plane ops will fail. Some machines in AMS are also unavailable.

  2. identified Oct 03, 2026, 08:08 AM UTC

    Those hosts are coming back online after a brief interruption. We are assessing the impact on MPG.

  3. monitoring Oct 03, 2026, 08:19 AM UTC

    All hosts are back online. MPGv2 control plane is fully operational now. Some MPGv1 clusters in AMS might be degraded while MPGv1's control plane recovers.

  4. monitoring Oct 03, 2026, 08:35 AM UTC

    All MPG clusters have recovered. We are monitoring for additional impact.

  5. resolved Oct 03, 2026, 08:57 AM UTC

    All impacted services are operational now.

Read the full incident report →

Minor October 1, 2026

Delayed ingestion of app logs

Detected by Pingoru
Oct 01, 2026, 01:11 AM UTC
Resolved
Oct 01, 2026, 02:49 AM UTC
Duration
1h 38m
Timeline · 5 updates
  1. investigating Oct 01, 2026, 01:11 AM UTC

    We're investigating delayed ingestion of app logs across all regions. New logs from machines may not be visible, but past logs are still available.

  2. identified Oct 01, 2026, 01:39 AM UTC

    We've identified the cause of the slowed log ingestion and are working on a fix.

  3. identified Oct 01, 2026, 02:27 AM UTC

    We've resolved the ingestion issue and our systems are processing the backlog of app logs. No logs have been lost.

  4. monitoring Oct 01, 2026, 02:35 AM UTC

    The backlog of app logs has been processed, and we're monitoring the health of the log cluster. No logs were lost.

  5. resolved Oct 01, 2026, 02:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 29, 2026

GRU Networking Issues

Detected by Pingoru
Sep 29, 2026, 07:30 PM UTC
Resolved
Sep 29, 2026, 07:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 29, 2026, 09:12 PM UTC

    We observed networking issues affecting a subset of our hosts in GRU from 19:37 UTC through 19:59 UTC. This affected platform operations requiring leases, private networking, and internet connectivity to some endpoints.

Read the full incident report →

Critical September 26, 2026

Network outage in AMS region

Detected by Pingoru
Sep 26, 2026, 07:53 PM UTC
Resolved
Sep 26, 2026, 07:53 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Sep 26, 2026, 08:10 PM UTC

    We are working with our upstream providers to restore connectivity to the AMS region.

  2. resolved Sep 26, 2026, 08:10 PM UTC

    This incident has been resolved.

  3. monitoring Sep 26, 2026, 08:10 PM UTC

    Connectivity is restored and the network is recovering.

Read the full incident report →

Major September 24, 2026

State database issues in GRU

Detected by Pingoru
Sep 24, 2026, 05:11 PM UTC
Resolved
Sep 24, 2026, 07:11 PM UTC
Duration
2h
Timeline · 4 updates
  1. identified Sep 24, 2026, 05:11 PM UTC

    We have identified a bug and are working on a fix.

  2. investigating Sep 24, 2026, 05:11 PM UTC

    We are investigating issues in GRU related to a migration of our distributed state database. Apps continue to run, but creating or updating machines in GRU region may fail. Connections to apps in GRU, or connections from clients near GRU region, may fail at this time

  3. monitoring Sep 24, 2026, 06:11 PM UTC

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

  4. resolved Sep 24, 2026, 07:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 24, 2026

Private Networking issues (6PN)

Detected by Pingoru
Sep 24, 2026, 03:11 PM UTC
Resolved
Sep 24, 2026, 03:37 PM UTC
Duration
26m
Timeline · 3 updates
  1. monitoring Sep 24, 2026, 03:11 PM UTC

    A fix has been implemented and we are seeing private networking error rates return to normal. We are continuing to monitor to ensure full recovery.

  2. investigating Sep 24, 2026, 03:11 PM UTC

    We are currently investigating this issue.

  3. resolved Sep 24, 2026, 04:12 PM UTC

    This incident has been resolved

Read the full incident report →

Major September 23, 2026

Partial Sprites outage

Detected by Pingoru
Sep 23, 2026, 07:12 PM UTC
Resolved
Sep 24, 2026, 02:12 AM UTC
Duration
7h
Timeline · 6 updates
  1. identified Sep 23, 2026, 07:12 PM UTC

    The issue has been identified and we are rolling out mitigations.

  2. investigating Sep 23, 2026, 07:12 PM UTC

    We are investigating intermittent API failures for users connecting near SJC.

  3. identified Sep 23, 2026, 09:10 PM UTC

    This issue is now occurring on regions other than SJC. We are still working on a fix.

  4. monitoring Sep 24, 2026, 12:11 AM UTC

    We have deployed another potential fix and are monitoring results.

  5. monitoring Sep 24, 2026, 02:10 AM UTC

    Sprites API performance has largely recovered and most users should no longer see errors creating, connecting to, or managing Sprites. We're still seeing a small number of intermittent errors and are investigating them before resolving this incident.

  6. resolved Sep 24, 2026, 03:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 23, 2026

Elevated private networking errors

Detected by Pingoru
Sep 23, 2026, 03:13 PM UTC
Resolved
Sep 23, 2026, 03:23 PM UTC
Duration
10m
Timeline · 3 updates
  1. monitoring Sep 23, 2026, 03:13 PM UTC

    A fix has been implemented are we are monitoring to ensure recovery.

  2. investigating Sep 23, 2026, 03:13 PM UTC

    We are investigating elevated errors with private networking between machines in some regions.

  3. resolved Sep 23, 2026, 04:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 23, 2026

Upstash unavailability in FRA region

Detected by Pingoru
Sep 23, 2026, 01:07 PM UTC
Resolved
Sep 23, 2026, 02:03 PM UTC
Duration
56m
Timeline · 4 updates
  1. investigating Sep 23, 2026, 01:07 PM UTC

    We are investigating an issue affecting Upstash services in the fra region. Customers may experience connection failures or service unavailability. We are working with Upstash to identify the cause and restore service. We’ll provide an update as soon as we have more information.

  2. resolved Sep 23, 2026, 02:13 PM UTC

    This incident has been resolved.

  3. monitoring Sep 23, 2026, 02:13 PM UTC

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

  4. resolved Sep 24, 2026, 08:12 AM UTC

    **Impact** From about 12:00 to 13:05 UTC, some clients got connection timeouts to their Redis databases. Affected were databases hosted in fra or gig, and clients whose connections were routed through fra or gig, even if their database is hosted in another region. **What happened** During a planned rolling upgrade, replicas in fra and gig did not finish draining and were left out of service. They were returned to Fly routing before they were ready to accept connections. Connections routed to them then timed out. **What we're changing** • We will be adding tooling to return a replica to service safely after maintenance. • We will be adding safety checks to our upgrade process. • We will make the upgrade procedure more resilient to errors like this one.

Read the full incident report →

Major September 23, 2026

IPv6 Networking Issues in DFW

Detected by Pingoru
Sep 23, 2026, 07:12 AM UTC
Resolved
Sep 23, 2026, 12:15 PM UTC
Duration
5h 3m
Timeline · 4 updates
  1. identified Sep 23, 2026, 07:12 AM UTC

    One of the internet transit providers upstream of the affected hosts is performing regional maintenance, which is expected to complete at 10:00AM UTC. IPv6 connectivity to and from destinations using that transit may be impacted during this time window.

  2. investigating Sep 23, 2026, 07:12 AM UTC

    We are investigating IPv6 connectivity issues on a subset of hosts in DFW region. Machines on impacted hosts may see inbound/outbound connectivity issues over IPv6. IPv4 connectivity is not impacted.

  3. identified Sep 23, 2026, 11:12 AM UTC

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

  4. resolved Sep 23, 2026, 01:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 15, 2026

Depot builder failures

Detected by Pingoru
Sep 15, 2026, 05:07 AM UTC
Resolved
Sep 15, 2026, 05:34 AM UTC
Duration
26m
Timeline · 4 updates
  1. identified Sep 15, 2026, 05:07 AM UTC

    We have identified an issue with deploying via Depot for users connecting through our SYD and JNB regions. Affected customers in these regions can deploy successfully using the --depot=false or --buildkit arguments to flyctl.

  2. investigating Sep 15, 2026, 05:07 AM UTC

    We are investigating reports of Depot builds failing for some customers. Affected customers can deploy successfully using the --depot=false or --buildkit arguments to flyctl.

  3. monitoring Sep 15, 2026, 05:07 AM UTC

    A fix has been implemented and we are monitoring builds. Standard flyctl builds should be working again for customers in all regions.

  4. resolved Sep 15, 2026, 06:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 12, 2026

Network issues in US West Coast

Detected by Pingoru
Sep 12, 2026, 10:07 PM UTC
Resolved
Sep 12, 2026, 10:12 PM UTC
Duration
5m
Timeline · 3 updates
  1. investigating Sep 12, 2026, 10:07 PM UTC

    We are investigating upstream network issues from US West Coast (SJC, LAX). Apps hosted in US West regions may experience higher latency or packet loss, and requests from clients physically located in US West may experience higher latency.

  2. monitoring Sep 12, 2026, 10:07 PM UTC

    Private networking between Fly Machines is resolved, and most outbound connections are healthy. We're continuing to monitor the network, and some issues will still be expected from clients physically located in US West until upstream transit issues are resolved.

  3. resolved Sep 12, 2026, 11:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 2, 2026

Sprites API Partial Outage

Detected by Pingoru
Sep 02, 2026, 11:03 PM UTC
Resolved
Sep 03, 2026, 12:41 AM UTC
Duration
1h 37m
Timeline · 3 updates
  1. investigating Sep 02, 2026, 11:03 PM UTC

    We're aware of a problem affecting a subset of Sprites users. We are investigating the source of the issue.

  2. monitoring Sep 03, 2026, 12:11 AM UTC

    Error rates have decreased. We are continuing to monitor the API health.

  3. resolved Sep 03, 2026, 01:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 2, 2026

Upstream network issues

Detected by Pingoru
Sep 02, 2026, 03:13 PM UTC
Resolved
Sep 02, 2026, 03:57 PM UTC
Duration
44m
Timeline · 5 updates
  1. identified Sep 02, 2026, 03:13 PM UTC

    We have put in some temporary mitigations along with our providers. However since the root cause of this issue lies within a bigger upstream transit provider, you may continue to see some elevated latency and connection issues in/around affected regions. We're still working closely with them to resolve the root cause.

  2. identified Sep 02, 2026, 03:13 PM UTC

    We're updating the affected region list to also include SJC since this seems to be a wider upstream issue in US West Coast.

  3. identified Sep 02, 2026, 03:13 PM UTC

    We have observed an upstream network issue in LAX. Connections to some destinations may see elevated latency and packet loss. We're working with our upstream to resolve this issue.

  4. monitoring Sep 02, 2026, 04:11 PM UTC

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

  5. resolved Sep 02, 2026, 04:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 2, 2026

API background job queue failure

Detected by Pingoru
Sep 02, 2026, 07:44 AM UTC
Resolved
Sep 02, 2026, 07:44 AM UTC
Duration
—
Timeline · 3 updates
  1. resolved Sep 02, 2026, 08:10 AM UTC

    This incident has been resolved.

  2. monitoring Sep 02, 2026, 08:10 AM UTC

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

  3. investigating Sep 02, 2026, 08:10 AM UTC

    We are investigating an issue with the background job runner for our API. Actions that require a background job, such as creating apps, assigning IP addresses, or creating/renewing certificates, may fail at this time.

Read the full incident report →

Notice August 31, 2026

HTTP/2 traffic disruptions

Detected by Pingoru
Aug 31, 2026, 03:30 PM UTC
Resolved
Aug 31, 2026, 03:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 31, 2026, 04:11 PM UTC

    A configuration update caused temporary failures for incoming HTTP/2 traffic for Fly Machines located on a subset of hosts for a few minutes. This incident has since been resolved. Managed Postgres depends on HTTP/2 and some control plane ops may have been affected as well. However, downstream Postgres connections were unlikely to have been affected by this since they do not use the HTTP2 handler.

Read the full incident report →

Minor August 31, 2026

Packet loss in ORD

Detected by Pingoru
Aug 31, 2026, 07:10 AM UTC
Resolved
Aug 31, 2026, 08:10 AM UTC
Duration
59m
Timeline · 3 updates
  1. investigating Aug 31, 2026, 07:10 AM UTC

    Due to an upstream provider, we are seeing ~50% packet loss on a subset of hosts in ORD. Some MPG clusters in ORD are slow to replicate as a result.

  2. monitoring Aug 31, 2026, 08:09 AM UTC

    Packet loss in ORD is improving and impacted services are recovering; we’re continuing to monitor for intermittent issues

  3. resolved Aug 31, 2026, 09:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 30, 2026

Sprite deletion jobs failing

Detected by Pingoru
Aug 30, 2026, 10:45 PM UTC
Resolved
Aug 30, 2026, 10:45 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 30, 2026, 10:45 PM UTC

    We saw Sprite deletion jobs failing between 21:18 and 22:05 UTC. This issue has been resolved.

Read the full incident report →

Minor August 28, 2026

Networking Issues in GRU

Detected by Pingoru
Aug 28, 2026, 10:10 PM UTC
Resolved
Aug 28, 2026, 10:36 PM UTC
Duration
26m
Timeline · 5 updates
  1. investigating Aug 28, 2026, 10:10 PM UTC

    We are investigating networking issues impacting some hosts in GRU (São Paulo, Brazil) region. Some apps in GRU may experience increased latency or packet loss.

  2. monitoring Aug 28, 2026, 10:10 PM UTC

    Networking performance in GRU has normalized and we are no longer seeing issues. We are continuing to monitor to ensure a full recovery.

  3. identified Aug 28, 2026, 11:11 PM UTC

    Our upstream provider has implemented a fix. Network performance in GRU has normalized.

  4. identified Aug 28, 2026, 11:11 PM UTC

    We are seeing a recurrance in networking issues in GRU. Some apps in the region may experience increased latency or packet loss. We are working with our upstream networking provider to resolve.

  5. resolved Aug 28, 2026, 11:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 28, 2026

Increased packet loss

Detected by Pingoru
Aug 28, 2026, 09:09 AM UTC
Resolved
Aug 28, 2026, 10:22 AM UTC
Duration
1h 13m
Timeline · 2 updates
  1. investigating Aug 28, 2026, 09:09 AM UTC

    We are currently investigating this issue.

  2. resolved Aug 28, 2026, 11:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 26, 2026

WireGuard gateway issues

Detected by Pingoru
Aug 26, 2026, 06:43 PM UTC
Resolved
Aug 26, 2026, 06:43 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Aug 26, 2026, 07:09 PM UTC

    We are investigating issues with our WireGuard gateways. Some CLI commands like `flyctl ssh console` or `flyctl proxy` may not work at this time. Apps continue to run.

  2. resolved Aug 26, 2026, 07:09 PM UTC

    This incident has been resolved.

  3. monitoring Aug 26, 2026, 07:09 PM UTC

    Our testing and monitoring indicates gateways should be back to normal; if you are still having problem using `flyctl ssh console`, try restarting the `flyctl` agent by `flyctl agent restart`.

  4. monitoring Aug 26, 2026, 07:09 PM UTC

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

Read the full incident report →

Minor August 24, 2026

Metrics in some regions are lagging behind

Detected by Pingoru
Aug 24, 2026, 11:09 AM UTC
Resolved
Aug 24, 2026, 01:24 PM UTC
Duration
2h 15m
Timeline · 3 updates
  1. investigating Aug 24, 2026, 11:09 AM UTC

    We are currently experiencing some metrics lag on servers in some regions. We are provisioning more metric processing instances to accommodate the backlog and catch up.

  2. monitoring Aug 24, 2026, 01:10 PM UTC

    All hosts have caught up with metrics and we're monitoring the situation

  3. resolved Aug 24, 2026, 02:10 PM UTC

    This is now resolved

Read the full incident report →

Major August 23, 2026

Network Issues in LAX Region

Detected by Pingoru
Aug 23, 2026, 02:09 AM UTC
Resolved
Aug 23, 2026, 02:10 AM UTC
Duration
1m
Timeline · 3 updates
  1. investigating Aug 23, 2026, 02:09 AM UTC

    We are investigating network issues in the Los Angeles region. Apps may experience higher latency or be unreachable at this time.

  2. monitoring Aug 23, 2026, 02:09 AM UTC

    Upstream networking issues have resolved.

  3. resolved Aug 23, 2026, 03:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 20, 2026

Temporary DNS resolution failure

Detected by Pingoru
Aug 20, 2026, 07:30 PM UTC
Resolved
Aug 20, 2026, 07:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 20, 2026, 08:15 PM UTC

    A BGP configuration error caused our Anycast DNS to route to some nodes without the proper DNS infrastructure. The issue was temporary and was resolved as soon as we removed that node from BGP.

Read the full incident report →

Notice August 20, 2026

Oauth/Macaroon Errors from flyctl

Detected by Pingoru
Aug 20, 2026, 02:08 PM UTC
Resolved
Aug 20, 2026, 02:16 PM UTC
Duration
8m
Timeline · 3 updates
  1. monitoring Aug 20, 2026, 02:08 PM UTC

    A fix has been deployed and this error should no longer be occurring. We're monitoring to ensure full recovery.

  2. identified Aug 20, 2026, 02:08 PM UTC

    We have identified an issue causing authentication errors for some operations from `flyctl`. These operations are failing with an error like: `This endpoint no longer accepts legacy OAuth tokens (starting with `fo1_`). Please use a macaroon token (starting with `fm2_`) instead. We have identified the issue and are rolling out a fix

  3. resolved Aug 20, 2026, 03:13 PM UTC

    This incident has been resolved.

Read the full incident report →