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.

Operational

Fly.io is operational. Verified . Official provider source.

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

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.

August 2026
Certificate issuance delays
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 have the size of TLS certificate issuance backlog under control, but are still seeing some remaining issues and are currently working to clean up the edge cases.
identified
We believe we have identified the issue and are releasing a fix.
investigating
We're currently investigating issues related to certificate issuance. Certificates may be delayed for new custom domains.
Managed Postgres v2 control plane issues in iad
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 investigating an issue with the control plane for Managed Postgres v2 in the IAD region. Creating new v2 clusters in the IAD region may fail at this time. Existing clusters continue to run, but may experience lagging backups.
July 2026
Capacity issues in CDG
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Creating machines in CDG region may fail at this time with an "no capacity available in cdg" message. Existing apps continue to run.
Outbound email issues
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
Our dashboard is failing to send outbound email. Emails such as new account verification or password reset may fail to send at this time.
Increased API latency
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating some database issues causing high latency on some API endpoints and dashboard operations. You may experience intermittent "503 service unavailable" errors at this time. Currently deployed apps continue to run.
High number of 5XX on the Machines API and dashboard
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
We are still working on fixing degraded Managed Postgres clusters.
monitoring
Some Managed Postgres v1 clusters are degraded. We are working on fixing them. Managed Postgres v2 is unaffected.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We've identified an internal service providing authentication to our Machines API has failed, our team is currently looking at our options for restoring this service. Existing Machines/Apps will continue to run as normal. Thank you for your patience.
identified
We've identified an internal service providing authentication to our Machines API has failed, our team is currently looking at our options for restoring this service. Existing Machines/Apps will continue to run as normal. Thank you for your patience.
investigating
We are continuing to investigate this issue.
investigating
Existing machines are unaffected. We are investigating the issue.
Egress IPv6 issues in BOM
minor Source not attested
Last archived state: resolved
View archived record details
identified
We have identified an upstream issue that is preventing egress IPv6 addresses in BOM from reaching parts of the internet, and we're currently working with an upstream provider to resolve this issue. Normal IPv6 addresses remain unaffected.
App creation failing
minor Source not attested
Last archived state: resolved
View archived record details
identified
An issue with our Machines API is causing app creations to fail in some cases. We are working on a fix.
Edge proxy issues
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 investigating increased connection latency and "connection reset" errors from our edge proxy. Apps continue to run, but requests may experience increased connection latency or fail at this time.
Partial outage in SJC
major Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results. Apps should be reachable at this point in time.
identified
A subset of hosts in SJC are currently offline. Some apps may be unreachable at this time.