Fly.io logo - Fly.io status monitoring

Is Fly.io Down?

Real-time status monitoring

All Systems Operational
30d uptime96.26%
96.26%
Uptime (30d)
274ms
Response Time
3
Incidents (7d)
1:33:26 PM
Last Checked

As of 3/10/2026, 1:33:26 PM, Fly.io is operational.

⚡ Get notified instantly when Fly.io goes down

Email alerts in under 60 seconds. Never check manually again.

Get Alerts — $9/mo

Embed Fly.io Status Badge

Show live Fly.io status in your README, documentation, or website

Fly.io Status
Markdown
[![Fly.io Status](https://apistatuscheck.com/api/badge/flyio)](https://apistatuscheck.com/api/flyio)
HTML
<a href="https://apistatuscheck.com/api/flyio"><img src="https://apistatuscheck.com/api/badge/flyio" alt="Fly.io Status" /></a>

Response Time (24h)

Min: 232msMax: 1291msAvg: 317ms
1291ms646ms0ms
<500ms
500-2000ms
>2000ms

Recent Incidents

majorresolved

Private networking issues in SYD region

Mar 7, 02:42 PM — Resolved Mar 7, 03:56 PM

This incident has been resolved.

noneresolved

Routing issues in NA regions

Mar 5, 07:24 PM — Resolved Mar 5, 07:50 PM

This incident has been resolved. Due to a BGP issue, we saw some North American traffic routed to edges in Singapore (sin). Users in North America would have seen additional request latency during this period.

majorresolved

Elevated GraphQL API errors

Mar 3, 08:18 PM — Resolved Mar 3, 09:15 PM

This incident was caused by a failed Redis node that powers our GraphQL API. We were able to recreate the Redis node and restore service. We are still investigating the root cause of the failure. In the mean time, all API endpoints now appear to be stable and errors have dropped to baseline level.

minorresolved

Cost Explorer fails to load

Mar 3, 10:50 AM — Resolved Mar 3, 12:10 PM

This incident has been resolved.

noneresolved

Certificates issues affecting API and proxy

Mar 3, 12:54 AM — Resolved Mar 3, 12:54 AM

Between 19:54 and 20:06 UTC, our Vault cluster serving app certificates was unavailable. This caused various API requests to fail, mainly operations on certificates but also app creates and IP assignments. As the failure mode was Vault requests hanging rather than failing immediately, TLS requests through fly-proxy for domains where the certificate was not cached on the local node remained open for a long time while proxy attempted to fetch the certificate; this caused some connections to fail as too many connection slots were taken up by requests waiting on Vault. The root cause of this incident was a partially completed update to the Vault cluster. We will be implementing safeguards in the proxy for this failure mode, as well as improving certificate storage longer-term.

Get Fly.io Outage Alerts

Be the first to know when Fly.io go down.

What is Fly.io?

Platform for running full-stack apps close to users worldwide

Fly.io Down? Try These Steps

  1. Check the official Fly.io status page for announcements
  2. Try refreshing your browser or clearing cache
  3. Check your internet connection
  4. Try accessing from a different network or VPN
  5. Check social media for reports from other users

Never get caught off guard by an outage

Get instant email alerts when APIs go down. Monitor up to 10 APIs for $9/mo — that's less than 1 minute of downtime costs.

Free tier available. No credit card required.