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.
July 2026
Some DFW hosts offline
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
A subset of hosts in DFW are currently offline, and we're investigating the issue.
Registry performance issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The fly.io registry is currently experiencing capacity constraints that reduced performance and may lead to temporary high latency or failed pushes. We are currently working to add capacity and restore service.
Delays starting Depot Builders in IAD
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are seeing improvements in builder performance, latency, and error rates. We are continuing to monitor for a full recovery.
Customers still seeing issues can trigger a fly-hosted builder based deploy with `fly deploy --depot=false`.
identified
We have identified an issue causing delays or failures when starting depoting builders located in the IAD region. Customers with builders in IAD may see delays or timeouts starting builds during `fly deploy`. We are working on a fix.
In the meantime customers can trigger a fly-hosted builder based deploy with `fly deploy --depot=false`. You can also change your builder region away from IAD via the `settings` tab of your Fly dashboard. We recommend DFW or ORD as alternate builder regions at ...
Partial Outage 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.
identified
We've identified the issue as a networking hardware failure impacting a subset of hosts at one of our Upstream providers in ORD. We are working with our provider to restore connectivity.
investigating
We are investigating an issue with one of our upstream providers in ORD. Machines across a subset of hosts may be unreachable or not running correctly. Deploys with machines on these hosts may fail at this time.
Some Managed Postgres clusters in ORD region may be unavailable or see connectivity issues at this time.
Partial outage in ORD
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Customer workloads are now starting and we're monitoring the affected hosts. Affected Managed Postgres instances will be investigated.
identified
Power restoration is ongoing and we're making sure the hosts are healthy before starting customer workloads to avoid issues. Customer impact remains and updates to come.
identified
Power restoration work in a subset of ORD is still in progress and impact remains ongoing for a subset of hosts and some Managed Postgres clusters.
identified
Our provider has advised us their facilities team is working on restoring the power, we'll provide another update as soon as we learn more.
identified
We've identified and reported power issues with one of our upstream providers in ORD. We're waiting for an update from our upstream for a resolution. Some Managed Postgres clusters in ORD will be unavailable due to placement.
investigating
We are investigating an issue with one of our upstream providers in ORD. Machines across a subset of hosts may be unreachable or not running correctly. Deploys with machines on these hosts may fail at this time.
Some Managed Postgres clusters in ORD region may be unavailable at this time.
Errors issuing new SSL certificates
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented upstream and certificates are being issued successfully. We will continue to monitor.
identified
The issue has been identified and we are awaiting a fix.
investigating
We are currently investigating errors when issuing new SSL certificates for hostnames.
Static Egress IPv6 issues in NRT
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 issues with static egress IPv6 addresses in NRT region. Apps using static egress IPs may experience connectivity failures to some destinations.
Elevated API Errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Background jobs have caught up and the API is fully operational. We are continuing to monitor service health.
identified
A fix has been put in place, and we are no longer seeing elevated API errors. Some dashboard actions will be delayed while background processing catches up.
identified
The cause of the errors has been identified and we are working on a fix.
investigating
We are investigating elevated errors with our GraphQL API and background job processing
June 2026
Egress IP issues in SIN and NRT
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 egress IP issues in SIN and NRT and are working on a fix. Some machines in SIN and NRT using egress IPs may temporarily lose connectivity or otherwise see degraded performance.
Delayed Metrics
majorSource not attested
Last archived state: resolved
View archived record details
identified
Almost all metrics have caught up aside from a small handful in `sin` and `syd`. We're continuing to monitor and expect these to complete in the next few hours.
identified
Backlogged metrics are still being processed. We're bringing extra processing capacity online to speed up the process.
identified
Backlogged metrics are still being processed and ingestion delays persist for some customers
identified
Backlogged metrics are still being processed and ingestion delays persist for some customers, but we’re continuing to see gradual improvement as the backlog continues to drain.
identified
Backlogged metrics data is still being processed, continue to monitor the situation while the system catches up.
identified
Metric ingestion is still delayed for some customers. We’re seeing gradual improvement and continue to monitor the situation while the system catches up.
identified
We are still in the process of increasing the metrics cluster throughput to catch up with metric backlog.
identified
We are continuing to see delayed metrics due to resource contention on a subset of metrics ingestion hosts, and we are working to rebalance ingestion traffic and reduce the backlog.
identified
We are continuing to see delayed metric exports from a number of hosts. Users will see delayed or missing metrics for machines on impacted hosts at this time.
identified
We've identified an issue on multiple hosts causing delayed metric ingestion into our hosted fly-metrics.net dashboards. We are working on a fix.
investigating
We are investigating issues with customer facing metrics in the fly-metrics.net dashboard. Users may see delayed or missing metrics at this time.
