Cloud & hosting
Is Fly.io down?
Live Fly.io status, measured independently. We probe 7 Fly.io endpoints from monitoring regions on every continent and record every outage we detect.
Fly.io is up
Our probes are reaching Fly.io normally from every region we check from.
Checked every minute from 6 regions on every continent.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website100% uptime, 30 days6 regions, 22 to 580 msCheckingp50249 msMedian responsep95421 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Machines API99.99% uptime, 30 days6 regions, 16 to 23 msCheckingp5019 msMedian responsep95170 msSlowest 5% of checks50 ms25024 h ago12 h agonow
- GraphQL API99.97% uptime, 30 days6 regions, 86 to 394 msCheckingp50229 msMedian responsep95360 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Image registry99.99% uptime, 30 days6 regions, 65 to 239 msCheckingp50127 msMedian responsep95218 msSlowest 5% of checks200 ms100024 h ago12 h agonow
- Dashboard99.99% uptime, 30 days6 regions, 181 to 956 msCheckingp50548 msMedian responsep95655 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Documentation99.99% uptime, 30 days6 regions, 140 to 566 msCheckingp50344 msMedian responsep95558 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Official status feed99.88% uptime, 30 days5 regions, 169 to 513 msCheckingp50407 msMedian responsep95568 msSlowest 5% of checks500 ms250024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Fly.io goes down
Follow these 7 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Fly.io goes down. They don't count against your monitor quota. Free plan, no card required.
About Fly.io outages
Fly.io runs containers as Machines in dozens of regions behind an Anycast proxy. Fly incidents are usually scoped to a region or a subsystem like the proxy, the Machines API, or a Postgres cluster, which makes multi-region probing especially useful.
What we check
Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website fly.io is unreachable. | httpfly.io | HTTP 200 | 1 min |
Machines API The Machines API is not answering. flyctl deploys, scaling, and restarts fail. | httpapi.machines.dev/v1/apps | HTTP 401 | 2 min |
GraphQL API The Fly GraphQL API is not answering. flyctl and the dashboard depend on it. | httpapi.fly.io/graphql | HTTP 200 | 2 min |
Image registry The Fly image registry is not answering its normal authentication challenge. Deploys cannot push images. | httpregistry.fly.io/v2/ | HTTP 401 | 2 min |
Dashboard The Fly dashboard is unreachable. | httpfly.io/app/sign-in | HTTP 200 | 2 min |
Documentation Fly's documentation is unreachable. | httpfly.io/docs/ | HTTP 200 | 5 min |
Official status feed Fly.io's status page is unreachable. | httpstatus.flyio.net/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Fly.io's official status page.
Embed a live Fly.io badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/fly-io?utm_source=badge)HTML
<a href="https://www.upti.my/status/fly-io?utm_source=badge"><img src="https://www.upti.my/status/fly-io/badge.svg" alt="Fly.io status"></a>Recent Fly.io outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Fly.io is up. Is your Fly.io integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Fly.io and fail quietly. Here is what teams that rely on Fly.io monitor on their side.
Your Fly apps, per region
Fly routes users to the nearest region, so an outage in one region only affects users near it. Probe from every continent to see the same picture your users do.
Multi-region uptime monitoringMachines that restart in a loop
A crash-looping Machine is Live between crashes. Heartbeats and recovery actions catch and fix the loop.
Self-healing infrastructure guideFly.io status: frequently asked questions
Fly incidents are frequently limited to one region or one host. Check the official page for that region, and compare our per-region probe results; if only one region fails, the problem is likely there rather than global.
Look at the per-region results above. If our probes fail from every region, Fly.io has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Fly.io may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Fly.io" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Fly.io: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Uptimy is not affiliated with Fly.io. Fly.io and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.