Loading status…
Loading status…
Fly.io status · Hosting & Platforms · checked (23s ago)
Also searched as Fly, Fly machines.
No — Fly.io is not down. All Fly.io systems are reported operational.
According to Fly.io's official status page, Fly.io was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Fly.io's feed reported no outage in 100.00% of our checks.
Everything above is read from Fly.io's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Fly.io in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Fly.io runs applications as Firecracker microVMs close to users, with its own Anycast network, volumes and managed Postgres. Deployment is by Docker image, and apps are usually spread across several regions at once, which shapes how its incidents are experienced.
Fly's status page reports per-region as well as globally, and separates the API and build pipeline from the running machines. Regional reporting is the point: an incident in one region degrades an app that is deployed there while the same app serves normally from everywhere else. Managed Postgres and volumes are reported separately from compute.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Fly.io's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Fly.io was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 23s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Fly.io's status endpoint.
Fly.io has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Fly.io posted itself — not every problem users hit.
resolved · Sep 15, 04:08 AM (5d ago)
resolved · Sep 12, 09:22 PM (7d ago)
resolved · Sep 2, 11:03 PM (17d ago)
resolved · Sep 2, 02:18 PM (17d ago)
resolved · Sep 2, 07:21 AM (17d ago)
resolved · Aug 31, 03:30 PM (19d ago)
resolved · Aug 31, 06:26 AM (19d ago)
resolved · Aug 30, 10:45 PM (20d ago)
resolved · Aug 28, 09:56 PM (22d ago)
resolved · Aug 28, 08:09 AM (22d ago)
resolved · Aug 26, 06:14 PM (24d ago)
resolved · Aug 24, 10:23 AM (26d ago)
resolved · Aug 23, 01:28 AM (28d ago)
resolved · Aug 20, 07:30 PM (30d ago)
resolved · Aug 20, 01:54 PM (30d ago)
resolved · Aug 20, 07:25 AM (30d ago)
resolved · Aug 18, 08:00 PM (32d ago)
resolved · Aug 17, 01:19 PM (33d ago)
resolved · Aug 14, 07:30 PM (36d ago)
resolved · Aug 13, 05:45 PM (37d ago)
Apps configured to scale to zero cold-start on the first request, which looks like a hang and is not an incident. A deploy that fails on health checks is your application, not the platform — read the release logs. Fly Postgres is a managed cluster you still operate, so a full disk or a failed leader election is yours to fix and will never appear on this page.
Fly.io is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.