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.
August 2026
Metrics in some regions are lagging behind
minorSource not attested
Last archived state: resolved
View archived record details
Metrics
monitoring
All hosts have caught up with metrics and we're monitoring the situation
investigating
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.
Network Issues in LAX Region
majorSource not attested
Last archived state: resolved
View archived record details
Customer Applications
monitoring
Upstream networking issues have resolved.
investigating
We are investigating network issues in the Los Angeles region. Apps may experience higher latency or be unreachable at this time.
Oauth/Macaroon Errors from flyctl
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed and this error should no longer be occurring. We're monitoring to ensure full recovery.
identified
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
MPG (v1) partially down in ORD
majorSource not attested
Last archived state: resolved
View archived record details
Management Plane - ORD
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We had an issue with the ord-0 Fly Kubernetes cluster, and many MPG clusters are failing to restart. Our MPG team is actively working on it.
No capacity in ARN
Source not attested
Last archived state: resolved
View archived record details
Deployments
investigating
New machines may fail to create in ARN because we lack capacity.
Secrets service outage
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have failed over the secrets database to a replica, and the Machines API appears healthy now. We are monitoring for any further issues.
identified
We are working to recover our secrets service after a failed deployment. Apps continue to run, but it is not possible to create new apps or update secrets at this time.
IPv6 Networking Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating degraded ipv6 networking on a subset of hosts
Increased app-not-found errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results
identified
We’ve deployed an additional mitigation to further reduce Corrosion retry pressure and are seeing improvement; we’re continuing to monitor while remaining affected nodes catch up.
identified
We’ve applied a mitigation to reduce the impact from Corrosion batch insertion retries and are continuing to monitor while affected nodes catch up.
identified
We have identified the issue as failed insertions in a subset of Corrosion batches. These failures trigger retries, which can cause timeouts for other batches.
investigating
We are currently investigating app-not-found errors returned by Machines API calls made shortly after creating new applications.
MPG IAD data plane degraded for new clusters
minorSource not attested
Last archived state: resolved
View archived record details
identified
High CPU pressure on a shared etcd instance is causing lags on MPG creation in the IAD region
MPG creation is failing in GRU due to lack of capacity
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We tweaked hosts to allow for more machine allocation. We'll be monitoring the region over the next hours.
identified
New MPG clusters may fail to create in GRU because we lack capacity.
