CheckUpstream measured Fly.io at 100.000% availability across 2830 independent checks (global · api). 103 incidents were recorded in the past 12 months; the most recent resolved 1 day ago after 2 hours. Status signals are polled from Fly.io's official Atlassian Statuspage status page, alongside independent probes and community reports.
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: 91 incidents · 340 of 365 days with none posted · 3d 7h 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.
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.
Time to resolve, from Fly.io's own incident posts (1 year)
Median time to resolve
1h 44m
Slowest 10% take longer than
9h 8m
From 91 incidents Fly.io published and resolved in the last 1 year, 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.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is Fly.io currently down?
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.
›When did Fly.io last have an outage?
Fly.io's last resolved incident started 1 day ago and lasted 1h 48m (degraded performance).
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.
›How do I monitor Fly.io in production?
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).
›How does CheckUpstream track Fly.io?
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.