Is Fly.io down?

Updates every minute

Two independent answers, side by side: what Infra Agent’s own checks observe from multiple regions, and what Fly.io reports on its official status page. We never mix the two.

Fly.io looks up right now

Infra Agent's checks are succeeding from all 3 of our regions, and Fly.io is not reporting any problems on its official status page.

Infra Agent checks

Independent · our own probes

No problems detected

Our checks are reaching Fly.io from all 3 regions.

Last checked 1 minute ago

Fly.io’s official status

Provider-reported · official feed

No problems reported

Fly.io reports "All Systems Operational" on its official status page.

Fly.io’s page updated about 4 hours agoFeed refreshed by us 1 minute ago
Open Fly.io’s status page

Our regional check results

The latest probe from each of our monitoring regions. A provider only counts as having problems when failures repeat across consecutive checks and more than one region.

Check regionMain website (fly.io)API (api.fly.io)Deploy registry (registry.fly.io)
Amsterdam, NL120 ms288 ms38 ms
Ashburn, US (East)100 ms32 ms15 ms
San Jose, US (West)43 ms248 ms23 ms

What we check

  • Main website (fly.io)https://fly.io
  • API (api.fly.io)https://api.fly.io/graphql
  • Deploy registry (registry.fly.io)https://registry.fly.io/v2/

Last 24 hours

Response times and failures from Infra Agent’s own checks of Fly.io.

0ms59ms117ms24h ago12h agonow
Average response time (all regions and endpoints)Half hours with failed checks

Recent Fly.io incidents

As reported by Fly.io on its official status page.

Fly.io looks down for you? Work through this

Fly.io incidents are usually scoped to one region, or to one platform service like deploys, networking, or the API, so the first job is figuring out which layer is actually broken.

  1. Ask Fly about your app first

    Run `fly status -a your-app` and `fly checks list -a your-app`. If your Machines show as started and passing health checks while your site is unreachable, the problem is likely in front of them (Fly's proxy or networking). If Machines are stopped or failing, look at `fly logs`, which may show your own app crashing.

  2. Deploys failing vs. running apps down

    Fly's build and deploy path (builders, the deploy registry) can have an incident while running Machines keep serving traffic normally. If only `fly deploy` fails, don't tear anything down. Wait out the incident instead of repeatedly redeploying.

  3. Check whether it's one region

    Fly's status page reports per-region components. Check which regions your app runs in (`fly regions list` or `fly scale show`) and compare. If one region is degraded and your app runs in several, Fly's proxy usually routes around it; a single-region app can be scaled out temporarily with `fly scale count`.

  4. API or dashboard down, apps fine

    If flyctl commands and fly.io/dashboard fail but your app still serves traffic, the incident is in Fly's control plane (api.fly.io). Running Machines don't depend on it, so avoid restarting anything you can't manage until the API recovers.

  5. Don't forget attached databases

    Fly Postgres clusters are apps in your organization too. Check them separately (`fly status -a your-db`, `fly checks list -a your-db`). An app that's up but erroring may just have lost its database, which narrows the incident to one region or one volume.

Check your own website

Provider looks fine but your site is down, or the other way around? Test any URL from our servers right now. No account needed.

About Fly.io

Fly.io runs full-stack apps and databases on machines in regions close to users around the world. Incidents are often scoped to one region or to specific platform services like deploys or networking, so one app can be affected while others keep running.

Also check: Is Vercel down? · Is DigitalOcean down? · Is Cloudflare down? · All providers

Infra Agent is an independent monitoring service and is not affiliated with, endorsed by, or sponsored by Fly.io. The Fly.io name is used for identification only. “Official status” information is republished from Fly.io’s public status feed and always links back to the source.

Fly.io outage FAQ

How do I tell if it's Fly.io or my own app that's down?

Run `fly status -a your-app` and `fly logs`. Machines running and health checks passing while users see errors points at Fly's proxy or networking; Machines crashing or restarting points at your app or its database. This page's checks probe Fly's website, control-plane API, and deploy registry independently of any single app.

Do Fly.io outages affect all regions at once?

Rarely. Most Fly.io incidents are scoped to specific regions or to one platform layer, such as deploys, the API, or networking in a datacenter. Multi-region apps often ride out a regional incident because Fly's proxy routes to healthy regions; single-region apps in the affected region feel it fully.

Doesn't Infra Agent itself run on Fly.io?

Yes. Full disclosure: Infra Agent's monitoring workers run on Fly.io machines in multiple regions. That makes our Fly.io checks well-placed but not fully independent of Fly: a catastrophic Fly-wide outage could affect this page itself. That's one more reason we always link Fly.io's official status page, which is hosted separately.

How often is this Fly.io status page updated?

Infra Agent probes Fly.io from every monitoring region roughly every 2 minutes and refreshes Fly.io's official status feed on the same schedule. Both timestamps are shown above, and the page re-checks automatically while you keep it open.

Free plan available

Don't find out from your users. Monitor your own stack.

Infra Agent watches your websites, APIs, and cron jobs every minute from multiple regions, and texts you the moment something breaks, whether it's Fly.io or your own server.