Fly.io
Infrastructure. Source: Fly.io status page.
History starts 2026-09-02 08:10 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 25+
- Median duration
- 44m
- p95 duration
- 7h 1m
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| Network, DNS, routing or connectivity failure | 7 |
| A provider or third-party service this vendor depends on failed | 5 |
| Orchestration, control plane, service discovery or load balancing failed | 3 |
| A zone, region or data center became unavailable | 2 |
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 2 |
| The text does not say enough to tell | 2 |
| Security incident or emergency response to a vulnerability | 1 |
| Login, tokens, certificates or credentials failed | 1 |
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 1 |
| A schema or data migration caused the failure | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Capacity issues in GRU region
Failure mode: A zone, region or data center became unavailable. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
We're experiencing low host capacity in GRU. Creating or starting Machines in the region may fail at this time. Remote builders in GRU are also impacted. We're actively provisioning additional capacity. As a temporary remediation, customers may consider creating resources in EWR...
-
resolved
We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Fly-metrics.net Grafana Dashboard Outage
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The fly-metrics.net hosted grafana and log search instance is currently unreachable as a result of . It will return once the host it is on is out of maintenance, approximately 20 minutes. Logs and Metrics shipped to other sources using things like Fly Telemetry or the Fly Log...
-
monitoring
The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance should now be reachable again. We're continuing to monitor for any issues as a result of .
-
resolved
The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance is now fully reachable.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Platform Wide Rolling Host Reboots
Failure mode: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We will be imminently applying rolling restarts across all hosts in our fleet for a critical maintenance. Customer Machines, volumes, and MPG cluster instances on each host will be unavailable while their host reboots. Each host will be unavailable for 15 - 20 minutes during the...
-
identified
We are beginning the rolling restart process of all hosts, beginning with the YYZ region. Machines, volumes, and MPG instances on hosts being rebooted will be unavailable for approximately 15-20 minutes during the restart. We will provide further updates as the rollout...
-
identified
Rolling host restarts are beginning in all regions. Machines, volumes, and MPG instances will be unavailable for approximately 15-20 minutes when their hosts are restarted during this process. Users should expect a period of disruption or downtime for their apps during this,...
-
identified
Host restarts are continuing in phases across all regions. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. Rollout phases were scheduled to...
-
identified
Host restarts are continuing in phases across all regions, with the first phase nearly complete. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to...
-
identified
Host restarts are continuing in phases across all regions, with the second phase nearly complete - at this point, roughly 25% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take...
-
identified
Host restarts are continuing in phases across all regions - at this point, roughly 40% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with...
-
identified
Host restarts are continuing in phases across all regions - at this point, roughly 50% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with...
-
identified
Host restarts are continuing in phases across all regions - at this point, roughly 65% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with...
-
identified
Host restarts are continuing in phases across all regions - at this point, roughly 70% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with...
-
identified
Host restarts are continuing in phases across all regions - at this point, roughly 80% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with...
-
identified
Host restarts are continuing in phases across all regions - at this point, roughly 85% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with...
-
identified
Host restarts are continuing in phases across all regions - at this point, roughly 90% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with...
-
identified
As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 90% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 2h30m. Only a subset of...
-
identified
As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 90% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 2h. Only a subset of hosts...
-
identified
As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 95% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 1h40m. Only a subset of...
-
identified
As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 95% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 1h30m. Only a subset of...
-
identified
As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 95% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 30m. Only a subset of...
-
monitoring
All host restarts have been completed and we are monitoring the fleet health. A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see this status on the personalized status page viewable at
-
resolved
All host restarts have been completed and the platform is operating normally. A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see further updates on the personalized status page viewable at
Excerpts are shortened. Read the full incident on Fly.io's status page.
Elevated errors creating apps and managing secrets
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We’re seeing elevated error rates and slow responses for some operations that create or change data. Creating new apps, setting or removing secrets, and some app deletions are affected. You may see 500 or 503 errors from `flyctl`, the Machines API, or the dashboard. Apps and...
-
monitoring
We’ve applied a fix for the elevated errors affecting app creation and secrets management. Error rates and response times have returned to normal. We’re continuing to monitor to confirm the issue is fully resolved.
-
resolved
Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Partial FRA network issues
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
resolved
Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes
Excerpts are shortened. Read the full incident on Fly.io's status page.
Historical logs are currently delayed
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
Our log ingestion pipeline is currently backed up. Historical logs will be delayed while the queue is processed.
-
monitoring
Logs are caught up and we are monitoring the situation
-
resolved
This has been resolved
Excerpts are shortened. Read the full incident on Fly.io's status page.
Sprite hosting outage
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
resolved
From approximately 2026-10-11 23:30 UTC through 2026-10-12 00:45 UTC some or all hosted sprites on the *.sprites.app subdomain were unavailable due to a certificate error. As of 00:45 UTC this incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Sprite creates failing
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Sprite creates are failing in all regions outside of Europe. We are investigating the cause.
-
identified
We have identified a potential issue and are applying a fix.
-
monitoring
Sprite pools are starting to recover and creates are succeeding. We are monitoring the pools as they refill.
-
resolved
The issue has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
LHR network issues
Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
We are working to resolve an issue with our BGP announcements in LHR (London, UK) region. Regional anycast and static egress IPs are currently not functional and anycast traffic is being rerouted to nearby regions.
-
monitoring
We have brought BGP back up in LHR and are monitoring recovery.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Impaired IPv6 connectivity in ORD
Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
IPv6 traffic is failing on a subset of machines in ORD. IPv6 connections may fail.
-
resolved
IPv6 upstream issue was solved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Partial outage in AMS
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
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.
-
identified
Those hosts are coming back online after a brief interruption. We are assessing the impact on MPG.
-
monitoring
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.
-
monitoring
All MPG clusters have recovered. We are monitoring for additional impact.
-
resolved
All impacted services are operational now.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Delayed ingestion of app logs
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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.
-
identified
We've identified the cause of the slowed log ingestion and are working on a fix.
-
identified
We've resolved the ingestion issue and our systems are processing the backlog of app logs. No logs have been lost.
-
monitoring
The backlog of app logs has been processed, and we're monitoring the health of the log cluster. No logs were lost.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
GRU Networking Issues
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
resolved
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.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Network outage in AMS region
Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We are working with our upstream providers to restore connectivity to the AMS region.
-
monitoring
Connectivity is restored and the network is recovering.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
State database issues in GRU
Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
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
-
identified
We have identified a bug and are working on a fix.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Private Networking issues (6PN)
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
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.
-
resolved
This incident has been resolved
Excerpts are shortened. Read the full incident on Fly.io's status page.
Partial Sprites outage
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are investigating intermittent API failures for users connecting near SJC.
-
identified
The issue has been identified and we are rolling out mitigations.
-
identified
This issue is now occurring on regions other than SJC. We are still working on a fix.
-
monitoring
We have deployed another potential fix and are monitoring results.
-
monitoring
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.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Elevated private networking errors
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are investigating elevated errors with private networking between machines in some regions.
-
monitoring
A fix has been implemented are we are monitoring to ensure recovery.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Upstash unavailability in FRA region
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
-
resolved
**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...
Excerpts are shortened. Read the full incident on Fly.io's status page.
IPv6 Networking Issues in DFW
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
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.
-
identified
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.
-
identified
We are continuing to work on a fix for this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Depot builder failures
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
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.
-
identified
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.
-
monitoring
A fix has been implemented and we are monitoring builds. Standard flyctl builds should be working again for customers in all regions.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Network issues in US West Coast
Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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.
-
monitoring
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.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Sprites API Partial Outage
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We're aware of a problem affecting a subset of Sprites users. We are investigating the source of the issue.
-
monitoring
Error rates have decreased. We are continuing to monitor the API health.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
Upstream network issues
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
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.
-
identified
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...
-
identified
We're updating the affected region list to also include SJC since this seems to be a wider upstream issue in US West Coast.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.
API background job queue failure
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fly.io's status page.