Looking for an update now? Check the current status, or follow Fly.io for future changes.
66.7%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.
May 2026
Private networking issues in SYD
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
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...
Elevated deployment errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We identified the issue and are working on a fix.
investigating
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/<org>/billing".
Networking issues 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.
identified
We are aware of increased latency and connection drops for clients located near Chicago (ORD) and are currently working on a fix.
Elevated latency for anycast ingress in ORD
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are seeing elevated latency for requests hitting the ORD edges.
Networking issues 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
We are currently investigating increased latency and dropped connections in ORD (Chicago).
Networking issues 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
We are currently investigating increased latency and dropped connections in ORD (Chicago).
Increased latency in SJC
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
We're still seeing connection issues originating from SJC/LAX/West Coast US and are still investigating.
monitoring
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.
investigating
We are currently investigating increased latency in SJC.
Private networking issues in SYD
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
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...
Elevated GraphQL API Latency
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 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
Source not attested
Last archived state: resolved
View archived record details
identified
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.
