Is Fly.io down?
Vendor reports no incidentWhat Fly.io reports
Fly.io reports no incident on its status page.
As of the last successful poll, 2026-11-05 13:39 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 2 minutes ago
Our checks of Fly.io pass from all 10 regions we check.
As of Nov 5, 2026, 2:02 PM UTC, RealUptime's checks of Fly.io passed in all 10 regions that returned a reading.
Fly.io reports: All systems operational (“All Systems Operational”)
Fly.io's own component breakdown, as they publish it
- Customer ApplicationsOperational
- DashboardOperational
- Machines APIOperational
- AMS - Amsterdam, NetherlandsOperational
- ARN - Stockholm, SwedenOperational
- BOM - Mumbai, IndiaOperational
- CDG - Paris, FranceOperational
- DFW - Dallas, Texas (US)Operational
- EWR - Secaucus, NJ (US)Operational
- FRA - Frankfurt, GermanyOperational
- GRU - Sao Paulo, BrazilOperational
- IAD - Ashburn, Virginia (US)Operational
- JNB - Johannesburg, South AfricaOperational
- LAX - Los Angeles, California (US)Operational
- LHR - London, United KingdomOperational
- NRT - Tokyo, JapanOperational
- ORD - Chicago, Illinois (US)Operational
- SIN - SingaporeOperational
- SJC - San Jose, California (US)Operational
- SYD - Sydney, AustraliaOperational
- YYZ - Toronto, CanadaOperational
- Persistent Storage (Volumes)Operational
- DeploymentsOperational
- Remote BuildsOperational
- LogsOperational
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
Check your own site while you wait on Fly.io
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, function by function
Fly.io answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- DashboardUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- GraphQL APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- MetricsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- RegistryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Email me when Fly.io reports an incident on its status page, and again when it reports it resolved.
Get an email when Fly.io reports an incident
Email me when Fly.io reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 590msstatus code: 200checked: Nov 5, 2026, 1:57 PM 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-WestChecks passinglatency: 611msstatus code: 200checked: Nov 5, 2026, 1:58 PM 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-CentralChecks passinglatency: 24msstatus code: 200checked: Nov 5, 2026, 1:46 PM 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.
- CanadaChecks passinglatency: 610msstatus code: 200checked: Nov 5, 2026, 1:51 PM 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 AmericaChecks passinglatency: 2578msstatus code: 200checked: Nov 5, 2026, 1:54 PM 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.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 699msstatus code: 200checked: Nov 5, 2026, 2:02 PM 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.
- UKChecks passinglatency: 30msstatus code: 200checked: Nov 5, 2026, 1:46 PM 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 PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 257msstatus code: 200checked: Nov 5, 2026, 1:43 PM 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 AsiaChecks passinglatency: 86msstatus code: 200checked: Nov 5, 2026, 1:54 PM 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.
- AustraliaChecks passinglatency: 1641msstatus code: 200checked: Nov 5, 2026, 1:51 PM 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 probe events
check 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 check readings and Fly.io's own claim at the time, side by side.
Full check history for Fly.io: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter
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 by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is Fly.io down?", https://realuptime.io/outages/fly-io. The readings change with every check, so give the date you read them.
What we check
What our check can and cannot see
A pass means the service returned real data from its own backend, with the content we expect. It does not show that every feature, account type or region works, or that sign-in is healthy.
Host checked: api.machines.dev