Looking for an update now? Check the current status, or follow Fly.io for future changes.
68.5%of 54 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
75.9%
29
7
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A fix has been implemented and we are monitoring the results.
identified
We have identified a bug and are working on a fix.
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
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.
monitoring
We have deployed another potential fix and are monitoring results.
identified
This issue is now occurring on regions other than SJC. We are still working on a fix.
identified
The issue has been identified and we are rolling out mitigations.
investigating
We are investigating intermittent API failures for users connecting near SJC.
A fix has been implemented and we are monitoring the results.
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.
We are continuing to work on a fix for this issue.
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.
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.
A fix has been implemented and we are monitoring builds. Standard flyctl builds should be working again for customers in all regions.
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.
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.
LAX - Los Angeles, California (US)SJC - San Jose, California (US)
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.
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.
Error rates have decreased. We are continuing to monitor the API health.
investigating
We're aware of a problem affecting a subset of Sprites users. We are investigating the source of the issue.
Legacy Incident Archive
106 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Elevated Sprites error rates in SIN
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our upstream paths have been fixed. We are monitoring the results.
identified
We are working with our upstream network provider to address periodic loss of connectivity over transit in ord
identified
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.
monitoring
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.
monitoring
Impacted NA backbones have been sidestepped where possible, and we're continuing to monitor network health.
monitoring
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.
investigating
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
majorSource not attested
Last archived state: resolved
View archived record details
identified
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
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The maintenance has been completed and control plane functions should recover to normal. We're monitoring for any further complications.
identified
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
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
An initial fix has been implemented and connectivity to all impacted clusters has been restored. We are continuing to monitor to ensure stable recovery.
identified
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
investigating
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
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Egress ips are broken in most of ORD, we are currently investigating this issue
Capacity issues in ARN region
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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
Source not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
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
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We're currently investigating an issue affecting flyctl ssh console functionality and machines' OIDC tokens.
May 2026
IPv6 outage for some machines in ORD
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We're working with our upstream providers to investigate an IPv6 networking failure in ORD.
