New Multi-region uptime checks and custom-domain status pages

Fly.io Outage History

Daily provider-status observations and published incident history for Fly.io.

Degraded performance

Fly.io is reporting degraded performance. Verified . Official provider source.

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

Jul 23Oct 20

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 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Upstream network issues
minor Observed active window 1h 41m

View incident details and source

Started:

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.
API background job queue failure
major Observed active window 23m

View incident details and source

Started:

Machines API
monitoring
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.
August 2026
Packet loss in ORD
minor Observed active window 1h 48m

View incident details and source

Started:

ORD - Chicago, Illinois (US)
monitoring
Packet loss in ORD is improving and impacted services are recovering; we’re continuing to monitor for intermittent issues
investigating
Due to an upstream provider, we are seeing ~50% packet loss on a subset of hosts in ORD. Some MPG clusters in ORD are slow to replicate as a result.
Networking Issues in GRU
minor Observed active window 43m

View incident details and source

Started:

GRU - Sao Paulo, Brazil
identified
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.
Increased packet loss
minor Observed active window 2h 15m

View incident details and source

Started:

Customer Applications
investigating
We are currently investigating this issue.
WireGuard gateway issues
minor Observed active window 35m

View incident details and source

Started:

monitoring
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
Networking performance degraded in BOM and SJC
minor Source 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
minor Source 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
major Source 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
minor Source 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
minor Source 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
major Source 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
major Source 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
major Source 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
major Source 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.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.