Fly.io Outage History
Past incidents and downtime events
Complete history of Fly.io outages, incidents, and service disruptions. Showing 50 most recent incidents.
June 2026(12 incidents)
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(29 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.
Capacity issues in EWR region
2 updates
This incident has been resolved.
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.
Networking performance degraded in BOM and SJC
3 updates
This incident has been resolved.
Network performance has been restored and we're continuing to monitor.
We're currently looking into this issue.
IPv6 outage for some machines in SIN
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to investigate this issue.
We are currently investigating this issue.
Network issues in SIN region
3 updates
This incident has been resolved.
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.
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.
IPv6 outage for some machines in ORD
2 updates
This incident has been resolved.
We're working with our upstream providers to investigate an IPv6 networking failure in ORD. Impacted apps may wish to temporarily provision additional capacity in nearby regions.
Networking issues in SIN
4 updates
This incident has been resolved.
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.
One of our upstreams is experiencing high packet loss and latency. We are actively working with them.
Machines may see high packet loss. Some MPGs are unable to connect to their config store and may be unreachable right now.
Networking issues with egress IP addresses in SYD
4 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We've identified the issue and are working on a fix.
We are currently investigating an issue affecting networking for new machines whose apps have assigned egress IP addresses in our SYD region
Issues with the Fly.io dashboard
5 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
We're currently investigating an issue where the Fly.io dashboard is failing to load in some cases.
Logs issues in IAD
2 updates
This incident has been resolved.
We are investigating an issue with logs and metrics in IAD region. New logs and metrics from machines in IAD region may be missing, but past logs/metrics are still accessible. Apps continue to run.
Proxy issues in SIN region
3 updates
This incident has been resolved.
A fix has been implemented and we are seeing proxy performance in SIN return to normal. All Managed Postgres clusters in the region are reachable. We are continuing to monitor to ensure stable recovery.
We are investigating issues with fly-proxy on a subset of hosts in the Singapore region. Apps are still running, but requests to/from some apps may fail, and some Managed Postgres clusters may be inaccessible.
Some Managed Postgres clusters in FRA are unreachable
6 updates
This incident has been resolved.
All affected clusters have recovered
Some of unreachable clusters are showing recovery. We are still fixing the root cause.
The issue has been identified and a fix is being implemented.
We are continuing to investigate this issue.
We are currently investigating this issue.
fly ssh console returns error 500
3 updates
This issue has been resolved, fly ssh console invocations are now working correctly.
We've deployed a fix and are monitoring as error rates normalize. `fly ssh console` should be working now.
A problem with our vault used to issue temporary certificates for SSH sessions is causing calls to `fly ssh console` and `fly console` to return error 500. Our team has identified the cause and is deploying a fix.
log search unavailable
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results. Logs should again be available through Log search in Grafana.
Log search in Grafana is currently unavailable. You may see `failed to make http request: 503` errors when accessing logs from fly-metrics.net at this time. App logs are still available using the `fly logs` command and in the Fly.io dashboard.
Upstash Redis Outage
5 updates
This incident has been resolved.
A fix has been implemented and we are seeing Upstash Redis connectivity return to normal across all regions. We continuing to monitor to ensure stable recovery.
We are continuing to work with Upstash on this issue. We have received reports of partial recovery for some users, however we are still seeing higher levels of degraded or failing connections connecting to Upstash Redis databases at this time.
We are continuing to work with Upstash on this issue.
We are working with Upstash to investigate issues with their Fly hosted Redis service. Users may see degraded or failing connections connecting to their Upstash Redis databases at this time.
Certificate Issuance failing due to LetsEncrypt Outage
3 updates
This incident has been resolved.
We are seeing recovery and certificates are now issuing normally. We are continuing to monitor to ensure full recovery.
Due to a service outage at LetsEncrypt, creating new certificates with `fly certs add` is failing. Existing certificates and `*.fly.dev` preview certificates are not impacted. For additional details please see LetsEncrypt's statuspage https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3
Connectivity issues in SJC
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Some hosts in SJC are currently experiencing an upstream network issue. Apps running on these hosts may be temporarily unavailable.
Intermittent machines issues in BOM
2 updates
This incident has been resolved.
Creation and updating of machines in BOM are affected. Some metrics and logs for resources in BOM may be delayed.
Elevated error rates on List Machines endpoint
2 updates
We mitigated the problem. The issue only affected apps having machines in the sin region.
We are currently investigating this issue.
Errors Setting/Updating Secrets
5 updates
This incident has been resolved.
Creation of new apps or changing secrets on existing apps fails
Creation of new apps or changing secrets on existing apps fails
We are continuing to investigate this issue.
We are currently investigating this issue.
Log search unavailable
3 updates
This incident has been resolved.
We have a mitigation in place and are monitoring results.
Log search in Grafana is currently unavailable. You may see `failed to make http request: 502` errors when accessing logs from fly-metrics.net at this time. App logs continue to be available using the `fly logs` command and in the Fly.io dashboard.
April 2026(9 incidents)
flyctl deploy creating new app instances
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 investigating an issue where fly deploy is creating new Fly machine instances rather than updating existing ones, leading to apps with a mixed state. We're currently investigating the issue. As a workaround, please try removing the "processes = [ "app" ]" line from your fly.toml configuration file and redeploying. Another workaround is to downgrade flyctl to 0.4.40 - this should resolve the issue in the meantime.
Slow machines operations in IAD region
5 updates
This incident has been resolved.
Network packet loss has returned to normal levels. We are monitoring the Machines API for stability.
We are continuing to investigate this issue.
We are deploying a partial mitigation while we continue investigating.
We are currently investigating the issue. Only a portion of machines within the region are impacted.
Errors when adding or editing Github integrations for deployments
5 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
We're investigating reports of "500" errors when trying to add a new Github integration or edit an existing Github integration in Fly.io/dashboard. This only affects "Launch an app from Github" or trying to change settings for an app set up this way. Existing integrations continue to work normally. It does not affect deploys done with `flyctl` or existing, running apps.
Errors (5xx, timeouts) in Fly.io dashboard
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 are investigating issues with web dashboard.
Increased latency in SIN
2 updates
This incident has been resolved.
We are currently working on resolving increased latencies in our Singapore region.
TLS certificate issues
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 Vault server that stores TLS certificates. Provisioning new TLS certificates may fail, and connecting to domains whose existing certificate has not yet been cached may fail.
Network issues in SYD
3 updates
This incident has been resolved.
We've identified the issue and applied a fix. All services should be working as normal.
We're currently investigating some networking issues in SYD. This is affecting a number of our central services.
Heightened latency in ORD
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating heightened network latency in ORD.
Managed Postgres control plane instability in NRT (Tokyo)
4 updates
This incident has been resolved.
A fix has been implemented and we are seeing MPG performance in NRT normalize. We are continuing to monitor to ensure a stable recovery
The issue has been identified and a fix is being implemented. Users with clusters in NRT may continue to see instability at this time
We are investigating instability in the MPG control plane in the NRT (Toyko, Japan) region causing unexpected cluster failovers. Clusters return to health shortly after, but some users with clusters in NRT may see dropped connections or degraded performance at this time.
📡 Tired of checking Fly.io status manually?
Better Stack monitors uptime every 30 seconds and alerts you instantly when Fly.io goes down.