StatOSS

Fly.io uptime

Fly.io, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

api.machines.dev/v1/appsEvery 5 minutes

Fly.io is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:52 UTC from Sydney, Australia: 401 in 18 ms.

Last 24 hours

Up for 51 d 10 h100% passed

287 checks, median 38 ms from Falkenstein, all passed

95% under 89 ms

Response time by region
EuropeEurope38 ms
N. AmericaNorth America13 ms
AsiaAsia17 ms
OceaniaOceania18 ms

Medians over this range, on one scale up to 100 ms.

Last 90 days

Up for 51 d 10 h100% passed

14,805 checks, median 42 ms from Falkenstein, all passed

95% under 110 ms

Response time by region
EuropeEurope42 ms
N. AmericaNorth America15 ms
AsiaAsia19 ms
OceaniaOceania19 ms

Medians over this range, on one scale up to 100 ms. Europe's places are scaled to Falkenstein, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

In the last 30 days Fly.io passed 8,862 of 8,862 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,014 of 2,0140
30 days100%8,862 of 8,8620
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany38 ms64 ms44 ms421
Helsinki, Finland106 ms171 ms116 ms42
Ashburn, USA13 ms19 ms14 ms502
Copenhagen, Denmark59 ms70 ms61 ms42
Singapore19 ms247 ms63 ms504
Sydney, Australia19 ms44 ms26 ms504

Outages

None detected since checks began on 30 Sep 2026.

What is checked

Runs apps as Firecracker machines in regions around the world. One of StatOSS's own check locations runs there.

StatOSS sends GET https://api.machines.dev/v1/apps?org_slug=personal and counts the check as passed on status 401 within 10 seconds. The Machines API's list of apps, which `fly deploy` and flyctl use to create and start machines. Without a token it answers 401.

Running apps are served by Fly's proxy and do not go through this API; they can stay up while it is down, and the other way round.

Fly.io reports its own incidents at status.flyio.net. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.