Is Fly.io down?
Operationalchecked moments ago
We reached Fly.io from all 10 regions we check.
No outage recorded in the 14 days we have measured Fly.io (since Aug 22, 2026).
Fly.io reports: All systems operational (“All Systems Operational”)
Fly.io's own component breakdown, as they publish it
- AMS - Amsterdam, NetherlandsOperational
- Customer ApplicationsOperational
- Fly Machine .internal DNSOperational
- Management Plane - ORDOperational
- Upstash for RedisOperational
- Usage Metrics APIOperational
- ARN - Stockholm, SwedenOperational
- DashboardOperational
- Fly Machine External DNSOperational
- Management Plane - IADOperational
- Stripe API ConnectionOperational
- Machines APIOperational
- Management Plane - FRAOperational
- *.flyio.net NameserversOperational
- Management Plane - GRUOperational
- BOM - Mumbai, IndiaOperational
- flydns.netOperational
- Management Plane - LAXOperational
- Persistent Storage (Volumes)Operational
- CDG - Paris, FranceOperational
- DeploymentsOperational
- Management Plane - SYDOperational
- Management Plane - AMSOperational
- Remote BuildsOperational
- DFW - Dallas, Texas (US)Operational
- LogsOperational
- Management Plane - LHROperational
- EWR - Secaucus, NJ (US)Operational
- Management Plane - NRTOperational
- MetricsOperational
- Management Plane - SINOperational
- SSL/TLS Certificate ProvisioningOperational
- Anycast EdgeOperational
- FRA - Frankfurt, GermanyOperational
- Management Plane - SJCOperational
- Fly Machine Image Registry 1Operational
- Management Plane - YYZOperational
- Fly Machine Image Registry 2Operational
- GRU - Sao Paulo, BrazilOperational
- IAD - Ashburn, Virginia (US)Operational
- CorrosionOperational
- JNB - Johannesburg, South AfricaOperational
- LAX - Los Angeles, California (US)Operational
- LHR - London, United KingdomOperational
- Phoenix.newOperational
- Support PortalOperational
- SpritesOperational
- NRT - Tokyo, JapanOperational
- ORD - Chicago, Illinois (US)Operational
- SIN - SingaporeOperational
- SJC - San Jose, California (US)Operational
- SYD - Sydney, AustraliaOperational
- YYZ - Toronto, CanadaOperational
These are Fly.io's components, named and scored by Fly.io. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Fly.io's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Fly.io response time, by region
Is it Fly.io, or is it you?
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Fly.io -- it cannot diagnose Fly.io's own systems.
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 499msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Fly.io normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestOperationallatency: 267msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Fly.io normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralOperationallatency: 460msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Fly.io normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaOperationallatency: 287msstatus code: 200checked: Sep 5, 2026, 1:53 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Fly.io normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaOperationallatency: 677msstatus code: 200checked: Sep 5, 2026, 1:56 AM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Fly.io normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 278msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Fly.io normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKOperationallatency: 93msstatus code: 200checked: Sep 5, 2026, 1:58 AM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Fly.io normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 238msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Fly.io normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaOperationallatency: 406msstatus code: 200checked: Sep 5, 2026, 1:47 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Fly.io normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaOperationallatency: 874msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Fly.io normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Fly.io, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Fly.io yet, which is not evidence that nothing is wrong.
Recent outages
measured entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Fly.io since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Fly.io covering any window you pick, with our measurements and Fly.io's own claim at the time, side by side.
Full availability history for Fly.io: 90-day availability by region, month-by-month uptime, and every incident on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversTell me when this goes down
Get told when we measure this
We will tell you when our probes stop reaching Fly.io, and again when they can reach it again. That is our own measurement from ten regions, not Fly.io's status page. No account, no card.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/fly-io)<a href="https://realuptime.io/outages/fly-io"><img src="https://realuptime.io/outages/fly-io/badge.svg?days=30" alt="Fly.io uptime measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What Fly.io's SLA implies, from our measurement
At or above your target
We measured none of downtime for Fly.io over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.
By our measurement there is no shortfall to claim for this period.
This is computed from our own probe measurements, not from Fly.io's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.