CheckUpstream measured Fly.io at 100.000% availability across 2829 independent checks (global · api). 103 incidents were recorded in the past 12 months; the most recent resolved earlier today after 2 hours. Status signals are polled from Fly.io's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2829 · p95 122ms (30d)
Share of our own checks against Fly.io endpoints that returned Fly.io's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 14 incidents · 21 of 30 days with none posted · 8h 4m of declared impact
Fewer incidents in the last 30 days than 6% of 232 tracked services.
Share of each window with no impact declared by Fly.io
7d
99.049%
30d
98.878%
90d
99.626%
180d
98.151%
1y
99.088%
Downtime like this can be refundable
If you're a paying Fly.io customer, outages in these windows may count against Fly.io's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Fly.io entitlement →Does Fly.io actually matter to you?
A Fly.io outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 14 incidents Fly.io published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Fly.io takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Live Fly.io status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/fly-io)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Fly.io is currently Operational. CheckUpstream tracks Fly.io in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Fly.io's last resolved incident started earlier today and lasted 1h 48m (degraded performance).
Looking for the live "is Fly.io down" view? See the Fly.io Live status page.
Aug 26, 18:14 UTC · resolved in 5m · Resolved
Aug 9, 02:50 UTC · resolved in 4h 20m · Resolved
Aug 5, 20:26 UTC · resolved in 24m · Resolved
Aug 4, 19:03 UTC · resolved in 8h 26m · Resolved
Aug 4, 14:53 UTC · resolved in 9h 7m · Resolved
Aug 1, 17:01 UTC · resolved in 1h 38m · Resolved
Jul 31, 13:34 UTC · resolved in 1h 21m · Resolved
Jul 29, 12:41 UTC · resolved in 48m · Resolved
Jul 20, 07:10 UTC · resolved in 9h 59m · Resolved
Jul 19, 03:48 UTC · resolved in 1h 12m · Resolved
Jul 16, 11:54 UTC · resolved in 25m · Resolved
Fly.io's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Fly.io endpoints. It is the share of checks that returned the expected response, not a figure taken from Fly.io's status page.
Sign up to CheckUpstream and add Fly.io to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Fly.io's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.