Skip to content

Outage tracker / Fly.io

Is Fly.io down?

I'm having a problem

Vendor reports no incidentWhat Fly.io reports

Fly.io reports no incident on its status page.

As of the last successful poll, 2026-10-23 14:53 UTC.

Fly.io's status page

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 1 minute ago

Our checks of Fly.io pass from all 10 regions we check.

As of Oct 23, 2026, 2:57 PM UTC, RealUptime's checks of Fly.io passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 2:57 PM UTC
US-East771 msChecks passing
US-West1238 msChecks passing
Europe173 msChecks passing
Asia-Pacific959 msChecks passing
US-Central1016 msChecks passing
Canada24 msChecks passing
UK26 msChecks passing
Southeast Asia1668 msChecks passing
Australia18 msChecks passing
South America2114 msChecks passing
their status pagetheir claim, not our reading

Fly.io reports: All systems operational (“All Systems Operational”)

from Fly.io's own status page, checked Oct 23, 2026, 2:27 PM UTC
Fly.io's own status page shows no incident, and our checks of Fly.io pass right now.

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

US-East
893msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 579ms2026-09-25 UTC: p95 612ms2026-09-26 UTC: p95 596ms2026-09-27 UTC: p95 340ms2026-09-28 UTC: p95 263ms2026-09-29 UTC: p95 332ms2026-09-30 UTC: p95 280ms2026-10-01 UTC: p95 403ms2026-10-02 UTC: p95 700ms2026-10-03 UTC: p95 579ms2026-10-04 UTC: p95 276ms2026-10-05 UTC: p95 209ms2026-10-06 UTC: p95 237ms2026-10-07 UTC: p95 347ms2026-10-08 UTC: p95 377ms2026-10-09 UTC: p95 310ms2026-10-10 UTC: p95 358ms2026-10-11 UTC: p95 406ms2026-10-12 UTC: p95 370ms2026-10-13 UTC: p95 327ms2026-10-14 UTC: p95 333ms2026-10-15 UTC: p95 304ms2026-10-16 UTC: p95 427ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 893ms
Sep 24Oct 8Oct 23
US-West
1.4sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 623ms2026-09-25 UTC: p95 533ms2026-09-26 UTC: p95 411ms2026-09-27 UTC: p95 221ms2026-09-28 UTC: p95 691ms2026-09-29 UTC: p95 297ms2026-09-30 UTC: p95 333ms2026-10-01 UTC: p95 564ms2026-10-02 UTC: p95 743ms2026-10-03 UTC: p95 635ms2026-10-04 UTC: p95 385ms2026-10-05 UTC: p95 417ms2026-10-06 UTC: p95 392ms2026-10-07 UTC: p95 278ms2026-10-08 UTC: p95 325ms2026-10-09 UTC: p95 457ms2026-10-10 UTC: p95 412ms2026-10-11 UTC: p95 351ms2026-10-12 UTC: p95 436ms2026-10-13 UTC: p95 653ms2026-10-14 UTC: p95 336ms2026-10-15 UTC: p95 289ms2026-10-16 UTC: p95 267ms2026-10-17 UTC: p95 573ms2026-10-18 UTC: p95 754ms2026-10-19 UTC: p95 901ms2026-10-20 UTC: p95 817ms2026-10-21 UTC: p95 779ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.4s
Sep 24Oct 8Oct 23
Europe
174msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 186ms2026-09-25 UTC: p95 113ms2026-09-26 UTC: p95 280ms2026-09-27 UTC: p95 255ms2026-09-28 UTC: p95 278ms2026-09-29 UTC: p95 179ms2026-09-30 UTC: p95 225ms2026-10-01 UTC: p95 527ms2026-10-02 UTC: p95 280ms2026-10-03 UTC: p95 272ms2026-10-04 UTC: p95 215ms2026-10-05 UTC: p95 239ms2026-10-06 UTC: p95 183ms2026-10-07 UTC: p95 153ms2026-10-08 UTC: p95 269ms2026-10-09 UTC: p95 261ms2026-10-10 UTC: p95 372ms2026-10-11 UTC: p95 242ms2026-10-12 UTC: p95 255ms2026-10-13 UTC: p95 240ms2026-10-14 UTC: p95 225ms2026-10-15 UTC: p95 212ms2026-10-16 UTC: p95 220ms2026-10-17 UTC: p95 360ms2026-10-18 UTC: p95 716ms2026-10-19 UTC: p95 887ms2026-10-20 UTC: p95 856ms2026-10-21 UTC: p95 213ms2026-10-22 UTC: p95 211ms2026-10-23 UTC: p95 174ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.5sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 807ms2026-09-25 UTC: p95 504ms2026-09-26 UTC: p95 819ms2026-09-27 UTC: p95 615ms2026-09-28 UTC: p95 597ms2026-09-29 UTC: p95 622ms2026-09-30 UTC: p95 691ms2026-10-01 UTC: p95 484ms2026-10-02 UTC: p95 513ms2026-10-03 UTC: p95 424ms2026-10-04 UTC: p95 426ms2026-10-05 UTC: p95 481ms2026-10-06 UTC: p95 453ms2026-10-07 UTC: p95 425ms2026-10-08 UTC: p95 348ms2026-10-09 UTC: p95 436ms2026-10-10 UTC: p95 266ms2026-10-11 UTC: p95 312ms2026-10-12 UTC: p95 328ms2026-10-13 UTC: p95 305ms2026-10-14 UTC: p95 331ms2026-10-15 UTC: p95 428ms2026-10-16 UTC: p95 541ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.5s
Sep 24Oct 8Oct 23
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 981ms2026-09-25 UTC: p95 756ms2026-09-26 UTC: p95 694ms2026-09-27 UTC: p95 317ms2026-09-28 UTC: p95 346ms2026-09-29 UTC: p95 361ms2026-09-30 UTC: p95 306ms2026-10-01 UTC: p95 231ms2026-10-02 UTC: p95 262ms2026-10-03 UTC: p95 349ms2026-10-04 UTC: p95 389ms2026-10-05 UTC: p95 418ms2026-10-06 UTC: p95 412ms2026-10-07 UTC: p95 313ms2026-10-08 UTC: p95 329ms2026-10-09 UTC: p95 499ms2026-10-10 UTC: p95 428ms2026-10-11 UTC: p95 529ms2026-10-12 UTC: p95 526ms2026-10-13 UTC: p95 368ms2026-10-14 UTC: p95 210ms2026-10-15 UTC: p95 282ms2026-10-16 UTC: p95 387ms2026-10-17 UTC: p95 591ms2026-10-18 UTC: p95 878ms2026-10-19 UTC: p95 812ms2026-10-20 UTC: p95 900ms2026-10-21 UTC: p95 355ms2026-10-22 UTC: p95 605ms2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
Canada
284msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 442ms2026-09-25 UTC: p95 433ms2026-09-26 UTC: p95 401ms2026-09-27 UTC: p95 479ms2026-09-28 UTC: p95 476ms2026-09-29 UTC: p95 360ms2026-09-30 UTC: p95 386ms2026-10-01 UTC: p95 298ms2026-10-02 UTC: p95 360ms2026-10-03 UTC: p95 358ms2026-10-04 UTC: p95 350ms2026-10-05 UTC: p95 282ms2026-10-06 UTC: p95 379ms2026-10-07 UTC: p95 414ms2026-10-08 UTC: p95 384ms2026-10-09 UTC: p95 211ms2026-10-10 UTC: p95 545ms2026-10-11 UTC: p95 558ms2026-10-12 UTC: p95 340ms2026-10-13 UTC: p95 400ms2026-10-14 UTC: p95 257ms2026-10-15 UTC: p95 266ms2026-10-16 UTC: p95 268ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 487ms2026-10-22 UTC: p95 305ms2026-10-23 UTC: p95 284ms
Sep 24Oct 8Oct 23
UK
154msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 204ms2026-09-25 UTC: p95 210ms2026-09-26 UTC: p95 358ms2026-09-27 UTC: p95 381ms2026-09-28 UTC: p95 363ms2026-09-29 UTC: p95 242ms2026-09-30 UTC: p95 243ms2026-10-01 UTC: p95 233ms2026-10-02 UTC: p95 265ms2026-10-03 UTC: p95 212ms2026-10-04 UTC: p95 160ms2026-10-05 UTC: p95 153ms2026-10-06 UTC: p95 128ms2026-10-07 UTC: p95 163ms2026-10-08 UTC: p95 277ms2026-10-09 UTC: p95 145ms2026-10-10 UTC: p95 125ms2026-10-11 UTC: p95 192ms2026-10-12 UTC: p95 391ms2026-10-13 UTC: p95 207ms2026-10-14 UTC: p95 242ms2026-10-15 UTC: p95 167ms2026-10-16 UTC: p95 131ms2026-10-17 UTC: p95 799ms2026-10-18 UTC: p95 856ms2026-10-19 UTC: p95 932ms2026-10-20 UTC: p95 966ms2026-10-21 UTC: p95 209ms2026-10-22 UTC: p95 218ms2026-10-23 UTC: p95 154ms
Sep 24Oct 8Oct 23
Southeast Asia
1.4sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 269ms2026-09-28 UTC: p95 410ms2026-09-29 UTC: p95 485ms2026-09-30 UTC: p95 171ms2026-10-01 UTC: p95 589ms2026-10-02 UTC: p95 720ms2026-10-03 UTC: p95 778ms2026-10-04 UTC: p95 777ms2026-10-05 UTC: p95 956ms2026-10-06 UTC: p95 640ms2026-10-07 UTC: p95 824ms2026-10-08 UTC: p95 825ms2026-10-09 UTC: p95 317ms2026-10-10 UTC: p95 177ms2026-10-11 UTC: p95 192ms2026-10-12 UTC: p95 269ms2026-10-13 UTC: p95 361ms2026-10-14 UTC: p95 434ms2026-10-15 UTC: p95 240ms2026-10-16 UTC: p95 352ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 997ms2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.4s
Sep 24Oct 8Oct 23
Australia
93msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 662ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 671ms2026-09-27 UTC: p95 498ms2026-09-28 UTC: p95 615ms2026-09-29 UTC: p95 974ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 893ms2026-10-02 UTC: p95 719ms2026-10-03 UTC: p95 553ms2026-10-04 UTC: p95 448ms2026-10-05 UTC: p95 450ms2026-10-06 UTC: p95 572ms2026-10-07 UTC: p95 848ms2026-10-08 UTC: p95 638ms2026-10-09 UTC: p95 238ms2026-10-10 UTC: p95 553ms2026-10-11 UTC: p95 479ms2026-10-12 UTC: p95 627ms2026-10-13 UTC: p95 471ms2026-10-14 UTC: p95 558ms2026-10-15 UTC: p95 506ms2026-10-16 UTC: p95 531ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 565ms2026-10-22 UTC: p95 390ms2026-10-23 UTC: p95 93ms
Sep 24Oct 8Oct 23
South America
2.6sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 571ms2026-09-25 UTC: p95 683ms2026-09-26 UTC: p95 460ms2026-09-27 UTC: p95 757ms2026-09-28 UTC: p95 933ms2026-09-29 UTC: p95 292ms2026-09-30 UTC: p95 301ms2026-10-01 UTC: p95 652ms2026-10-02 UTC: p95 492ms2026-10-03 UTC: p95 530ms2026-10-04 UTC: p95 394ms2026-10-05 UTC: p95 496ms2026-10-06 UTC: p95 507ms2026-10-07 UTC: p95 445ms2026-10-08 UTC: p95 690ms2026-10-09 UTC: p95 414ms2026-10-10 UTC: p95 360ms2026-10-11 UTC: p95 372ms2026-10-12 UTC: p95 653ms2026-10-13 UTC: p95 833ms2026-10-14 UTC: p95 963ms2026-10-15 UTC: p95 898ms2026-10-16 UTC: p95 578ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.8s2026-10-23 UTC: p95 2.6s
Sep 24Oct 8Oct 23

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

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.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Fly.io's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 771msstatus code: 200checked: Oct 23, 2026, 2:55 PM UTC
      0 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-West
      Checks passinglatency: 1238msstatus code: 200checked: Oct 23, 2026, 2:57 PM UTC
      0 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-Central
      Checks passinglatency: 1016msstatus code: 200checked: Oct 23, 2026, 2:53 PM UTC
      0 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.
    • Canada
      Checks passinglatency: 24msstatus code: 200checked: Oct 23, 2026, 2:53 PM UTC
      0 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 America
    Checks passinglatency: 2114msstatus code: 200checked: Oct 23, 2026, 2:53 PM UTC
    0 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.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 173msstatus code: 200checked: Oct 23, 2026, 2:52 PM UTC
      0 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.
    • UK
      Checks passinglatency: 26msstatus code: 200checked: Oct 23, 2026, 2:53 PM UTC
      0 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 Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 959msstatus code: 200checked: Oct 23, 2026, 2:55 PM UTC
      0 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 Asia
      Checks passinglatency: 1668msstatus code: 200checked: Oct 23, 2026, 2:39 PM UTC
      0 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.
    • Australia
      Checks passinglatency: 18msstatus code: 200checked: Oct 23, 2026, 2:53 PM UTC
      0 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

Degraded Edge Performance, 1mdeclared on their status page2026-10-22
Capacity issues in GRU region, 6h 59mdeclared on their status page2026-10-20
Fly-metrics.net Grafana Dashboard Outage, 1h 16mdeclared on their status page2026-10-16
Platform Wide Rolling Host Reboots, 12h 53mdeclared on their status page2026-10-16
Elevated errors creating apps and managing secrets, 2h 4mdeclared on their status page2026-10-15
Partial FRA network issues, 1mdeclared on their status page2026-10-15
Historical logs are currently delayed, 4h 25mdeclared on their status page2026-10-13
Sprite hosting outage, 1mdeclared on their status page2026-10-11

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 servers

Put this badge in your README

Fly.io uptime by RealUptime's checksLive, from this page's own readings.
[![Fly.io uptime by RealUptime's checks](https://realuptime.io/outages/fly-io/badge.svg?days=30)](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>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.machines.dev/v1/platform/regions
secondary
https://fly.io/
secondary
https://status.flyio.net/api/v2/status.json

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

RealUptime is not affiliated with Fly.io; the name identifies what we checked, and nothing here speaks for Fly.io's own team. We send a single web request to Fly.io from 10 regions on our own schedule and time the response. We do not see inside Fly.io's systems, do not use an account or real transaction, and are not the same signal Fly.io's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Fly.io is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.