Is Fly.io Down?

No — Fly.io is up

Reachable from all 18 checked regions

Average response time: 148ms

Last checked just now · 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

169ms

Avg response, 30 days

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

30-day history

29-day clean streak

Jul 25 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

35ms

DNS 0ms TCP 0ms TLS 16ms TTFB 27ms

arn

27ms

DNS 0ms TCP 0ms TLS 8ms TTFB 18ms

bom

314ms

DNS 0ms TCP 0ms TLS 15ms TTFB 138ms

cdg

35ms

DNS 0ms TCP 0ms TLS 13ms TTFB 27ms

dfw

28ms

DNS 0ms TCP 0ms TLS 11ms TTFB 21ms

ewr

54ms

DNS 0ms TCP 0ms TLS 11ms TTFB 38ms

fra

56ms

DNS 0ms TCP 0ms TLS 9ms TTFB 38ms

gru

30ms

DNS 0ms TCP 0ms TLS 13ms TTFB 24ms

iad

31ms

DNS 0ms TCP 0ms TLS 16ms TTFB 26ms

jnb

788ms

DNS 0ms TCP 0ms TLS 10ms TTFB 313ms

lax

33ms

DNS 0ms TCP 0ms TLS 15ms TTFB 26ms

lhr

32ms

DNS 0ms TCP 0ms TLS 14ms TTFB 25ms

nrt

420ms

DNS 0ms TCP 0ms TLS 13ms TTFB 165ms

ord

118ms

DNS 0ms TCP 0ms TLS 11ms TTFB 64ms

sin

31ms

DNS 0ms TCP 0ms TLS 13ms TTFB 22ms

sjc

29ms

DNS 0ms TCP 0ms TLS 12ms TTFB 24ms

syd

522ms

DNS 0ms TCP 0ms TLS 11ms TTFB 212ms

yyz

85ms

DNS 0ms TCP 0ms TLS 13ms TTFB 40ms

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 all 18 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 — 18 of them answered the most recent check.
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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required