Fly.io Outage History
Past incidents and downtime events
Complete history of Fly.io outages, incidents, and service disruptions. Showing 50 most recent incidents.
August 2026(2 incidents)
Inbound connection failure to Fly Apps
1 update
A BGP misconfiguration while provisioning new edge capacity caused most traffic from Europe endpoints to be dropped, between 14:50 UTC and 15:02 UTC. The misconfiguration has been fixed and we are implementing safeguards against this kind of issue in the future.
Managed Postgres v2 control plane issues in iad
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are investigating an issue with the control plane for Managed Postgres v2 in the IAD region. Creating new v2 clusters in the IAD region may fail at this time. Existing clusters continue to run, but may experience lagging backups.
July 2026(17 incidents)
Capacity issues in CDG
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Creating machines in CDG region may fail at this time with an "no capacity available in cdg" message. Existing apps continue to run.
Outbound email issues
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Our dashboard is failing to send outbound email. Emails such as new account verification or password reset may fail to send at this time.
Increased API latency
2 updates
This incident has been resolved.
We are investigating some database issues causing high latency on some API endpoints and dashboard operations. You may experience intermittent "503 service unavailable" errors at this time. Currently deployed apps continue to run.
High number of 5XX on the Machines API and dashboard
8 updates
This incident has been resolved.
We are still working on fixing degraded Managed Postgres clusters.
Some Managed Postgres v1 clusters are degraded. We are working on fixing them. Managed Postgres v2 is unaffected.
A fix has been implemented and we are monitoring the results.
We've identified an internal service providing authentication to our Machines API has failed, our team is currently looking at our options for restoring this service. Existing Machines/Apps will continue to run as normal. Thank you for your patience.
We've identified an internal service providing authentication to our Machines API has failed, our team is currently looking at our options for restoring this service. Existing Machines/Apps will continue to run as normal. Thank you for your patience.
We are continuing to investigate this issue.
Existing machines are unaffected. We are investigating the issue.
Egress IPv6 issues in BOM
2 updates
This incident has been resolved.
We have identified an upstream issue that is preventing egress IPv6 addresses in BOM from reaching parts of the internet, and we're currently working with an upstream provider to resolve this issue. Normal IPv6 addresses remain unaffected.
Brief Flycast / MPG interruption in YYZ
1 update
A bad deployment momentarily caused issues with Flycast connectivity, and, by extension, MPG, in our YYZ region. The deployment was immediately rolled back and connectivity was restored shortly after.
Edge proxy issues
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are investigating increased connection latency and "connection reset" errors from our edge proxy. Apps continue to run, but requests may experience increased connection latency or fail at this time.
App creation failing
2 updates
This incident has been resolved.
An issue with our Machines API is causing app creations to fail in some cases. We are working on a fix.
Partial outage in SJC
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results. Apps should be reachable at this point in time.
A subset of hosts in SJC are currently offline. Some apps may be unreachable at this time.
Some DFW hosts offline
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
A subset of hosts in DFW are currently offline, and we're investigating the issue.
Delays starting Depot Builders in IAD
3 updates
This incident has been resolved.
A fix has been implemented and we are seeing improvements in builder performance, latency, and error rates. We are continuing to monitor for a full recovery. Customers still seeing issues can trigger a fly-hosted builder based deploy with `fly deploy --depot=false`.
We have identified an issue causing delays or failures when starting depoting builders located in the IAD region. Customers with builders in IAD may see delays or timeouts starting builds during `fly deploy`. We are working on a fix. In the meantime customers can trigger a fly-hosted builder based deploy with `fly deploy --depot=false`. You can also change your builder region away from IAD via the `settings` tab of your Fly dashboard. We recommend DFW or ORD as alternate builder regions at this time. Please note, your builder region can differ from the region your machines are in.
Registry performance issues
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The fly.io registry is currently experiencing capacity constraints that reduced performance and may lead to temporary high latency or failed pushes. We are currently working to add capacity and restore service.
Partial Outage in ORD
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We've identified the issue as a networking hardware failure impacting a subset of hosts at one of our Upstream providers in ORD. We are working with our provider to restore connectivity.
We are investigating an issue with one of our upstream providers in ORD. Machines across a subset of hosts may be unreachable or not running correctly. Deploys with machines on these hosts may fail at this time. Some Managed Postgres clusters in ORD region may be unavailable or see connectivity issues at this time.
Partial outage in ORD
7 updates
This incident has been resolved.
Customer workloads are now starting and we're monitoring the affected hosts. Affected Managed Postgres instances will be investigated.
Power restoration is ongoing and we're making sure the hosts are healthy before starting customer workloads to avoid issues. Customer impact remains and updates to come.
Power restoration work in a subset of ORD is still in progress and impact remains ongoing for a subset of hosts and some Managed Postgres clusters.
Our provider has advised us their facilities team is working on restoring the power, we'll provide another update as soon as we learn more.
We've identified and reported power issues with one of our upstream providers in ORD. We're waiting for an update from our upstream for a resolution. Some Managed Postgres clusters in ORD will be unavailable due to placement.
We are investigating an issue with one of our upstream providers in ORD. Machines across a subset of hosts may be unreachable or not running correctly. Deploys with machines on these hosts may fail at this time. Some Managed Postgres clusters in ORD region may be unavailable at this time.
Errors issuing new SSL certificates
4 updates
This incident has been resolved.
A fix has been implemented upstream and certificates are being issued successfully. We will continue to monitor.
The issue has been identified and we are awaiting a fix.
We are currently investigating errors when issuing new SSL certificates for hostnames.
Static Egress IPv6 issues in NRT
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are investigating issues with static egress IPv6 addresses in NRT region. Apps using static egress IPs may experience connectivity failures to some destinations.
Elevated API Errors
5 updates
This incident has been resolved.
Background jobs have caught up and the API is fully operational. We are continuing to monitor service health.
A fix has been put in place, and we are no longer seeing elevated API errors. Some dashboard actions will be delayed while background processing catches up.
The cause of the errors has been identified and we are working on a fix.
We are investigating elevated errors with our GraphQL API and background job processing
June 2026(22 incidents)
Delayed Metrics
12 updates
This incident has been resolved.
Almost all metrics have caught up aside from a small handful in `sin` and `syd`. We're continuing to monitor and expect these to complete in the next few hours.
Backlogged metrics are still being processed. We're bringing extra processing capacity online to speed up the process.
Backlogged metrics are still being processed and ingestion delays persist for some customers
Backlogged metrics are still being processed and ingestion delays persist for some customers, but we’re continuing to see gradual improvement as the backlog continues to drain.
Backlogged metrics data is still being processed, continue to monitor the situation while the system catches up.
Metric ingestion is still delayed for some customers. We’re seeing gradual improvement and continue to monitor the situation while the system catches up.
We are still in the process of increasing the metrics cluster throughput to catch up with metric backlog.
We are continuing to see delayed metrics due to resource contention on a subset of metrics ingestion hosts, and we are working to rebalance ingestion traffic and reduce the backlog.
We are continuing to see delayed metric exports from a number of hosts. Users will see delayed or missing metrics for machines on impacted hosts at this time.
We've identified an issue on multiple hosts causing delayed metric ingestion into our hosted fly-metrics.net dashboards. We are working on a fix.
We are investigating issues with customer facing metrics in the fly-metrics.net dashboard. Users may see delayed or missing metrics at this time.
Egress IP issues in SIN and NRT
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are aware of egress IP issues in SIN and NRT and are working on a fix. Some machines in SIN and NRT using egress IPs may temporarily lose connectivity or otherwise see degraded performance.
Metrics currently experiencing issues
2 updates
This incident has been resolved.
We are currently investigating an issue with our metrics cluster.
IPv6 Connectivity Issues in EWR
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
One of our upstream providers is experiencing IPv6 network connectivity problems in EWR. Apps with machines on affected hosts may have impacted connectivity to certain IPv6 destinations while they investigate and resolve this issue.
Deploys defaulting to Fly-hosted Builders
3 updates
This incident has been resolved.
We are seeing improvements in Depot builder provision times and are switching the default deploy strategy back to them. We will continue to monitor builder performance closely. Users with a preference can trigger a Fly builder based deploy with `fly deploy --depot=false` or use `fly deploy --depot=true` to force a depot-based deployment.
We are investigating delays provisioning Depot backed builders for deploys. We have switched the default `fly deploy` strategy to use fly hosted builders at this time. Users can still trigger a depot based deploy with `fly deploy --depot=true`
Elevated control plane latency
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We're addressing elevated control plane latency and saturation affecting the BOM and NRT regions. Apps with machines in this region might experience longer response times and possible timeouts (502 errors).
Degraded networking in North America
4 updates
This incident has been resolved.
Some 6PN Private Networking traffic remains impacted into and out of our LAX region, pending upstream resolution.
Most networking is largely healthy between primary North American regions. Some Machines may see ongoing packet loss and higher latency communicating with other Machines on certain routes. We're continuing to monitor the backbone health upstream.
We are currently investigating degraded network performance between sites in NA due to an upstream incident
Network issues in SIN, NRT
2 updates
This incident has been resolved.
Our upstream provider is continuing to experience network issues in SIN and NRT regions. Apps running in those regions may be unreachable or experience high packet loss at this time.
SIN, NRT network issues
5 updates
This incident has been resolved.
We are continuing to experience network issues with an upstream provider in SIN and NRT regions.
A fix has been implemented and we are monitoring the results.
Our upstream provider has identified the issue and is working on a fix. Apps running in NRT (Tokyo) region may also have issues reaching certain destinations at this time.
We are investigating an upstream network issue in the SIN (Singapore) region. Apps may be unreachable or have higher packet loss.
Log search unavailable
4 updates
Most queued historical logs have been ingested and should now be available through log search. Log ingestion rates have returned to normal levels.
We've applied a fix for this issue. Historical logs are currently backfilling. We will post an update once logs have finished backfilling and current logs are being ingested normally.
Log search is available; however, new app logs since ~1 hour ago are missing and new logs are not being ingested. We are continuing to investigate.
We are investigating an issue causing application log search to be unavailable. This is affecting the Fly Metrics log search panels, and historical application logs initially returned from the `fly logs` command. Streaming logs using `fly logs`, the Live Logs page in the dashboard, and Fly Log Shipper services continue to work as expected.
Network Issues in SIN
5 updates
This incident has been resolved.
Network connectivity in SIN has been fully restored. We're continuing to monitor.
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.
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.
We are currently investigating network connectivity issues in the SIN region. Hosted apps may be unavailable.
Macaroon Auth + Machines API Issues
9 updates
This incident has been resolved and we are seeing all platform functions operate normally.
A fix has been implemented and we are monitoring the results.
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.
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.
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.
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.
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.
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
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.
MPG cluster provisioning is broken
2 updates
This incident has been resolved.
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.
Elevated Sprites error rates in SIN
3 updates
This incident has been resolved.
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.
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
Increased network latency in North America
8 updates
This incident has been resolved.
Our upstream paths have been fixed. We are monitoring the results.
We are working with our upstream network provider to address periodic loss of connectivity over transit in ord
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.
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.
Impacted NA backbones have been sidestepped where possible, and we're continuing to monitor network health.
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.
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.
Ingress Traffic issues in GRU
2 updates
This incident has been resolved.
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.
Emergency maintenance of Petsem causing some control plane errors
3 updates
This incident has been resolved.
The maintenance has been completed and control plane functions should recover to normal. We're monitoring for any further complications.
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.
Managed Postgres Control Plane Issues in IAD
4 updates
This incident has been resolved.
An initial fix has been implemented and connectivity to all impacted clusters has been restored. We are continuing to monitor to ensure stable recovery.
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
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.
egress ips are broken in ORD
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Egress ips are broken in most of ORD, we are currently investigating this issue
Capacity issues in ARN region
2 updates
This incident has been resolved.
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.
Consul cluster degradation
3 updates
We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.
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.
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.
Issues with flyctl ssh console and Machines OIDC
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We're currently investigating an issue affecting flyctl ssh console functionality and machines' OIDC tokens.
May 2026(9 incidents)
IPv6 outage for some machines in ORD
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We're working with our upstream providers to investigate an IPv6 networking failure in ORD.
Private networking issues in SYD
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
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.
Elevated deployment errors
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We identified the issue and are working on a fix.
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".
Networking issues in ORD
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are aware of increased latency and connection drops for clients located near Chicago (ORD) and are currently working on a fix.
Networking issues in ORD
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating increased latency and dropped connections in ORD (Chicago).
Networking issues in ORD
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating increased latency and dropped connections in ORD (Chicago).
Increased latency in SJC
6 updates
This incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
We're still seeing connection issues originating from SJC/LAX/West Coast US and are still investigating.
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.
We are currently investigating increased latency in SJC.
Private networking issues in SYD
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
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.
Elevated GraphQL API Latency
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are investigating elevated API Latency. Users may see delays or errors creating apps, as well as on some dashboard pages.
📡 Tired of checking Fly.io status manually?
Better Stack monitors uptime every 30 seconds and alerts you instantly when Fly.io goes down.