Is Fly.io Down?

No — Fly.io is up

Reachable from all 17 checked regions

Average response time: 194ms

Last checked 19 minutes ago · checks run every 30 minutes

Official status page: https://status.flyio.net

Fly.io uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

200ms

Avg response, 30 days

Measured from multiple regions every 30 minutes. Percentages count only checks that returned an availability answer — 80 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

80-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

47ms

DNS 12ms TCP 0ms TLS 14ms TTFB 44ms

arn

32ms

DNS 0ms TCP 0ms TLS 9ms TTFB 31ms

cdg

176ms

DNS 143ms TCP 0ms TLS 14ms TTFB 174ms

dfw

102ms

DNS 75ms TCP 0ms TLS 9ms TTFB 100ms

ewr

136ms

DNS 82ms TCP 0ms TLS 12ms TTFB 120ms

fra

69ms

DNS 0ms TCP 0ms TLS 14ms TTFB 47ms

gru

44ms

DNS 12ms TCP 0ms TLS 14ms TTFB 43ms

iad

97ms

DNS 64ms TCP 0ms TLS 17ms TTFB 96ms

jnb

790ms

DNS 56ms TCP 0ms TLS 11ms TTFB 370ms

lax

41ms

DNS 10ms TCP 0ms TLS 13ms TTFB 37ms

lhr

41ms

DNS 10ms TCP 0ms TLS 12ms TTFB 37ms

nrt

483ms

DNS 119ms TCP 0ms TLS 12ms TTFB 284ms

ord

161ms

DNS 30ms TCP 0ms TLS 11ms TTFB 107ms

sin

121ms

DNS 82ms TCP 0ms TLS 12ms TTFB 120ms

sjc

85ms

DNS 5ms TCP 0ms TLS 14ms TTFB 55ms

syd

742ms

DNS 6ms TCP 0ms TLS 9ms TTFB 301ms

yyz

131ms

DNS 6ms TCP 0ms TLS 12ms TTFB 78ms

What Fly.io does

Fly.io is an application hosting platform that runs full-stack apps and databases close to users worldwide. It deploys applications as micro-VMs using Firecracker, the same technology behind AWS Lambda, and distributes them across a global network of data centers. Fly.io is popular for deploying Elixir, Go, and Node.js applications with low-latency requirements.

What an outage looks like

When Fly.io is down, deployed applications may become unreachable or respond with 502/503 errors. The flyctl CLI may fail to connect for deployments and management commands. Machine scaling may stop working, and applications may not restart after crashes. DNS resolution for .fly.dev domains may fail.

What to do about it

Check community.fly.io/c/incidents and status.flyio.net for current incidents. Fly.io outages are sometimes region-specific, so check if your application's primary region is affected. If you have multi-region deployments, traffic should automatically fail over to healthy regions.

Is it down for everyone, or just you?

If this page says Fly.io is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Vercel

Netlify

AWS

Cloudflare

Fly.io outage FAQ

Does a Fly.io outage affect all regions?

Fly.io outages are often region-specific rather than global. Your application may be down in one region while working fine in others. If you've configured multi-region deployments, Fly.io's Anycast routing will direct traffic to the nearest healthy region automatically.

What happens to my Fly.io Machines during an outage?

Running Machines typically continue operating during control plane outages. However, if the compute infrastructure in your region is affected, Machines may become unreachable. Machines that were stopped won't be able to start, and auto-scaling won't function until the control plane recovers.

Can I deploy during a Fly.io outage?

No, deployments require Fly.io's control plane and builder infrastructure. During an outage, flyctl commands will fail or time out. Your existing deployment continues running as long as the compute infrastructure is healthy. Wait for the incident to resolve before attempting new deployments.

Is my Fly.io Postgres database affected by platform outages?

Fly.io Postgres runs as a regular Fly Machine, so it shares the same infrastructure. If the compute layer in your database's region is down, your database will be unreachable. For critical databases, consider running replicas in multiple regions for failover capability.

How we measure this

We request Fly.io's public endpoint every 30 minutes from Fly.io regions across six continents — the most recent check ran from 17 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Fly.io publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Fly.io goes down

This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required