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
fly ssh console returns error 500
Source not attested
Last archived state: resolved
View archived record details
monitoring
We've deployed a fix and are monitoring as error rates normalize. `fly ssh console` should be working now.
identified
A problem with our vault used to issue temporary certificates for SSH sessions is causing calls to `fly ssh console` and `fly console` to return error 500.
Our team has identified the cause and is deploying a fix.
log search unavailable
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results. Logs should again be available through Log search in Grafana.
investigating
Log search in Grafana is currently unavailable. You may see `failed to make http request: 503` errors when accessing logs from fly-metrics.net at this time. App logs are still available using the `fly logs` command and in the Fly.io dashboard.
Upstash Redis Outage
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are seeing Upstash Redis connectivity return to normal across all regions. We continuing to monitor to ensure stable recovery.
investigating
We are continuing to work with Upstash on this issue. We have received reports of partial recovery for some users, however we are still seeing higher levels of degraded or failing connections connecting to Upstash Redis databases at this time.
investigating
We are continuing to work with Upstash on this issue.
investigating
We are working with Upstash to investigate issues with their Fly hosted Redis service. Users may see degraded or failing connections connecting to their Upstash Redis databases at this time.
Certificate Issuance failing due to LetsEncrypt Outage
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We are seeing recovery and certificates are now issuing normally. We are continuing to monitor to ensure full recovery.
identified
Due to a service outage at LetsEncrypt, creating new certificates with `fly certs add` is failing.
Existing certificates and `*.fly.dev` preview certificates are not impacted. For additional details please see LetsEncrypt's statuspage https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3
Connectivity issues in SJC
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Some hosts in SJC are currently experiencing an upstream network issue. Apps running on these hosts may be temporarily unavailable.
Intermittent machines issues in BOM
minorSource not attested
Last archived state: resolved
View archived record details
identified
Creation and updating of machines in BOM are affected. Some metrics and logs for resources in BOM may be delayed.
Elevated error rates on List Machines endpoint
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue.
Errors Setting and Updating Secrets on Apps
majorSource not attested
Last archived state: resolved
View archived record details
investigating
Creation of new apps or changing secrets on existing apps fails
investigating
Creation of new apps or changing secrets on existing apps fails
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
Log search unavailable
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have a mitigation in place and are monitoring results.
investigating
Log search in Grafana is currently unavailable. You may see `failed to make http request: 502` errors when accessing logs from fly-metrics.net at this time. App logs continue to be available using the `fly logs` command and in the Fly.io dashboard.
April 2026
flyctl deploy creating new app instances
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 issue has been identified and a fix is being implemented.
investigating
We're investigating an issue where fly deploy is creating new Fly machine instances rather than updating existing ones, leading to apps with a mixed state. We're currently investigating the issue.
As a workaround, please try removing the "processes = [ "app" ]" line from your fly.toml configuration file and redeploying. Another workaround is to downgrade flyctl to 0.4.40 - this should resolve the issue in the meantime.
