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
LAX - Los Angeles, California (US)SJC - San Jose, California (US)
monitoring
A fix has been implemented and we are monitoring the results.
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.
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 closely with them to resolve the root cause.
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.
A fix has been implemented and we are monitoring the results.
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.
We are seeing a recurrance in networking issues in GRU. Some apps in the region may experience increased latency or packet loss. We are working with our upstream networking provider to resolve.
monitoring
Networking performance in GRU has normalized and we are no longer seeing issues. We are continuing to monitor to ensure a full recovery.
investigating
We are investigating networking issues impacting some hosts in GRU (São Paulo, Brazil) region. Some apps in GRU may experience increased latency or packet loss.
Our testing and monitoring indicates gateways should be back to normal; if you are still having problem using `flyctl ssh console`, try restarting the `flyctl` agent by `flyctl agent restart`.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating issues with our WireGuard gateways. Some CLI commands like `flyctl ssh console` or `flyctl proxy` may not work at this time. Apps continue to run.
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.
