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
A fix has been implemented and we are monitoring the results.
identified
We have identified a bug and are working on a fix.
investigating
We are investigating issues in GRU related to a migration of our distributed state database. Apps continue to run, but creating or updating machines in GRU region may fail. Connections to apps in GRU, or connections from clients near GRU region, may fail at this time
Sprites API performance has largely recovered and most users should no longer see errors creating, connecting to, or managing Sprites. We're still seeing a small number of intermittent errors and are investigating them before resolving this incident.
monitoring
We have deployed another potential fix and are monitoring results.
identified
This issue is now occurring on regions other than SJC. We are still working on a fix.
identified
The issue has been identified and we are rolling out mitigations.
investigating
We are investigating intermittent API failures for users connecting near SJC.
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue affecting Upstash services in the fra region. Customers may experience connection failures or service unavailability.
We are working with Upstash to identify the cause and restore service. We’ll provide an update as soon as we have more information.
We are continuing to work on a fix for this issue.
identified
One of the internet transit providers upstream of the affected hosts is performing regional maintenance, which is expected to complete at 10:00AM UTC. IPv6 connectivity to and from destinations using that transit may be impacted during this time window.
investigating
We are investigating IPv6 connectivity issues on a subset of hosts in DFW region. Machines on impacted hosts may see inbound/outbound connectivity issues over IPv6. IPv4 connectivity is not impacted.
A fix has been implemented and we are monitoring builds. Standard flyctl builds should be working again for customers in all regions.
identified
We have identified an issue with deploying via Depot for users connecting through our SYD and JNB regions. Affected customers in these regions can deploy successfully using the --depot=false or --buildkit arguments to flyctl.
investigating
We are investigating reports of Depot builds failing for some customers. Affected customers can deploy successfully using the --depot=false or --buildkit arguments to flyctl.
LAX - Los Angeles, California (US)SJC - San Jose, California (US)
monitoring
Private networking between Fly Machines is resolved, and most outbound connections are healthy. We're continuing to monitor the network, and some issues will still be expected from clients physically located in US West until upstream transit issues are resolved.
investigating
We are investigating upstream network issues from US West Coast (SJC, LAX). Apps hosted in US West regions may experience higher latency or packet loss, and requests from clients physically located in US West may experience higher latency.
Error rates have decreased. We are continuing to monitor the API health.
investigating
We're aware of a problem affecting a subset of Sprites users. We are investigating the source of the issue.
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
Networking performance degraded in BOM and SJC
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Network performance has been restored and we're continuing to monitor.
investigating
We're currently looking into this issue.
IPv6 outage for some machines in SIN
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 continuing to investigate this issue.
investigating
We are currently investigating this issue.
Network issues in SIN region
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our upstream provider has implemented a fix and all apps and Managed Postgres clusters are now reachable.
For the time being, ingress traffic is being re-routed to other regions, so users around the Singapore area may experience higher latency.
investigating
We are investigating network issues in the Singapore region. Apps may experience higher latency or be unreachable at this time. Some Managed Postgres clusters may be unreachable.
IPv6 outage for some machines in ORD
Source not attested
Last archived state: resolved
View archived record details
investigating
We're working with our upstream providers to investigate an IPv6 networking failure in ORD. Impacted apps may wish to temporarily provision additional capacity in nearby regions.
Networking issues in SIN
minorSource not attested
Last archived state: resolved
View archived record details
identified
All MPGs in SIN are reachable again. We are seeing high latency to the affected provider. This may affect a subset of machines hosted in SIN.
identified
One of our upstreams is experiencing high packet loss and latency. We are actively working with them.
investigating
Machines may see high packet loss. Some MPGs are unable to connect to their config store and may be unreachable right now.
Networking issues with egress IP addresses 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
We've identified the issue and are working on a fix.
investigating
We are currently investigating an issue affecting networking for new machines whose apps have assigned egress IP addresses in our SYD region
Issues with the Fly.io dashboard
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 are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We're currently investigating an issue where the Fly.io dashboard is failing to load in some cases.
Logs issues in IAD
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue with logs and metrics in IAD region. New logs and metrics from machines in IAD region may be missing, but past logs/metrics are still accessible. Apps continue to run.
Proxy issues in SIN region
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are seeing proxy performance in SIN return to normal. All Managed Postgres clusters in the region are reachable. We are continuing to monitor to ensure stable recovery.
investigating
We are investigating issues with fly-proxy on a subset of hosts in the Singapore region. Apps are still running, but requests to/from some apps may fail, and some Managed Postgres clusters may be inaccessible.
Some Managed Postgres clusters in FRA are unreachable
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
All affected clusters have recovered
identified
Some of unreachable clusters are showing recovery. We are still fixing the root cause.
identified
The issue has been identified and a fix is being implemented.
