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.
March 2026
Fly ssh console command failing
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified an issue causing new `fly ssh console` connections to fail with 500 errors. A fix is in progress.
Connection Issues in SJC
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Between 13:55 and 14:03 UTC machines and MPG clusters hosted in the SJC region saw elevated connection errors. Users may have seen errors connecting to or from most machines in the region, as well as with deployments or updates to machines in the region.
Networking has returned to normal in the region, and we are continuing to monitor closely to ensure stable recovery.
Machines failing to start in DFW
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The team is currently rolling out additional capacity in DFW which should help ease Machine start failures across the region.
investigating
We are investigating reports of machines failing to start in the DFW (Dallas) region with "insufficient memory" errors. This may cause deployment failures for applications running in DFW.
Our team is actively working to restore full capacity in the region. If you are affected, deploying to an alternate region may serve as a temporary workaround.
We will provide updates as the situation progresses.
Elevated 502 errors when starting Sprites in LAX and ORD
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We're currently investigating an elevated number of 502 errors when attempting to start Sprites in LAX and ORD.
Sprite Operations: 401 errors for certain organizations
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Organizations with numerical prefixes might experience failing sprite operations ( like creating a sprite, listing sprites, etc... ) due to 401 errors
monitoring
Root cause has been identified and a fix has been applied
investigating
Organizations with numerical prefixes might experience failing sprite operations ( like creating a sprite, listing sprites, etc... ) due to 401 errors
monitoring
Organizations with numerical prefixes might experience failing sprite operations ( like creating a sprite, listing sprites, etc... ) due to 401 errors
Sprites Operations: 401 errors for certain organizations
Source not attested
Last archived state: resolved
View archived record details
monitoring
Organizations with names prefixed with numerical digits may experience 401 errors. Affected operations include actions such as Sprite creation, listing, etc...
A fix has been implemented and we are monitoring the results!
