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.
April 2026
Metrics currently experiencing issues
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We have implemented a fix. We're monitoring the cluster for further issues.
investigating
We are currently investigating an issue with our metrics cluster.
GraphQL API / Dashboard Issues
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have restored GraphQL and dashboard availability, but some actions (e.g. app state updates) may still be delayed.
investigating
We are investigating issues with our GraphQL API and web dashboard
March 2026
Low Capacity in SIN and AMS regions
Source not attested
Last archived state: resolved
View archived record details
monitoring
We've freed up additional room in the SIN and AMS regions and are monitoring capacity.
monitoring
We've freed up additional room in the SIN and AMS regions and are monitoring capacity.
identified
We are currently investigating capacity issues in SIN and AMS regions that are affecting:
- Machine Create and Start events
- Deployments, due to affected, degraded Remote Builders
- Sprite startup from cold state
identified
This may also affect:
- Remote builders in AMS and SIN regions, which could currently be experiencing degraded performance or failures.
- Sprites starting from a cold state, which may experience failures in starting
identified
We are currently investigating elevated errors when creating and starting machines in the SIN and AMS regions. Choosing other regions to create or deploy may help in the meantime
Low capacity in IAD
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
With the additional capacity we've brought online, machine start failure rates in IAD have now recovered. We'll continue to monitor IAD capacity.
identified
We've brought some additional capacity online in IAD and are seeing improvements, and we're continuing to work on adding more and freeing up additional room.
investigating
We're continuing to evaluate our options for increasing short-term capacity in the IAD region.
investigating
We're currently investigating capacity issues in IAD that is preventing machine starts (machine creates are currently unaffected). This may result in deploys failing to complete (even for apps outside of the IAD region). As a workaround, using legacy Fly builders explicitly located in another region (i.e., `FLY_REMOTE_BUILDER_REGION=lhr fly deploy --depot=false --recreate-builder`) may help in the meantime.
Machine Creates Failing in ORD Region
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've implemented a fix and have seen error rates for machine creates in ORD drop off. We're continuing to monitor the results.
identified
We've identified the cause of this increased failure rate and a fix is in progress. We are seeing most creates in ORD succeed at this time, though failure rate is still above baseline.
investigating
We are continuing to investigate this issue. We are seeing 408 errors decreasing in ORD, though still above baseline.
investigating
We are currently investigating elevated errors creating machines in the ORD (Chicago, Illinois) region. Users may see `failed to launch VM: request returned non-2xx status: 408` errors when creating, updating, or scaling machines in ORD.
Existing, already running machines in the ORD region continue to run as normal.
Network issues in FRA region
criticalSource not attested
Last archived state: resolved
View archived record details
identified
Some Managed Postgres clusters in FRA region are still unreachable, we are investigating this issue.
monitoring
Apps and Managed Postgres clusters in FRA region should be back online at this time. We are monitoring for any further issues.
investigating
We are investigating network issues in FRA region. Apps and/or Managed Postgres clusters in the region may be inaccessible at this time.
Backend errors when trying to use Grafana to view logs
Source not attested
Last archived state: resolved
View archived record details
monitoring
We've deployed a fix and are monitoring the results. Logs are now be visible on Grafana.
identified
Using the Logs panel in Grafana at https://fly-metrics.net/ will show a 502 error from the backend and won't show any logs. You can use `fly logs` or the live log viewer directly on https://fly.io/dashboard to view streaming logs for the time being.
investigating
Using the Logs panel in Grafana at https://fly-metrics.net/ will show a 502 error from the backend and won't show any logs. You can use `fly logs` or the live log viewer directly on https://fly.io/dashboard to view streaming logs for the time being.
Machines failing to start in DFW
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Machine start success rates in DFW have improved but we are continuing to monitor and make further adjustments. We will provide updates as the situation progresses.
monitoring
In addition to freeing up existing capacity, the team has provisioned new capacity in DFW and we are monitoring the results.
monitoring
We freed up some capacity on our workers to allow for successful Machine starts.
investigating
The Machines start failure rate is elevated in DFW.
Metrics currently experiencing issues
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix. There has been approximately 1h of lost metrics from 06:07UTC. We're monitoring the cluster for further issues
investigating
We are currently investigating an issue with our metrics cluster.
IPv6 networking issues in SJC region
majorSource 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 intermittent network issues in SJC region impacting outbound public IPv6 access from Machines. Connecting to IPv6 internet resources from apps hosted in SJC region may be slow or fail at this time.
IPv4 access, as well as 6PN private networking, are unaffected.
