Skip to main content
Vendor reliability

Vendor record

Fly.io

Vendor reports Partial Outage

Checked

Front door check counts and Fly.io’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Fly.io endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.machines.dev
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Fly.io product, region or your app worked.

How we count front door checks

Fly.io says

Incident posts from Fly.io’s status page, with its titles, impact levels and times. They say what Fly.io chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

15

incidents Fly.io posted, last 30 days

Median recorded duration: 1h 27m. From 7 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Platform Wide Rolling Host Reboots

    Major

    Started, per Fly.io

    Latest status Fly.io postedInvestigating. No resolution posted.

  • Elevated errors creating apps and managing secrets

    Major

    Started, per Fly.io

    Latest status Fly.io postedInvestigating. No resolution posted.

  • Historical logs are currently delayed

    Minor

    Started, per Fly.io

    Latest status Fly.io postedInvestigating. No resolution posted.

  • Sprite hosting outage

    Major

    Started, per Fly.io

    Latest status Fly.io postedInvestigating. No resolution posted.

  • Sprite creates failing

    Critical

    Started, per Fly.io

    Latest status Fly.io postedInvestigating. No resolution posted.

15 older records

  • LHR network issues

    Major

    Started, per Fly.io

    Latest status Fly.io postedInvestigating. No resolution posted.

  • Partial outage in AMS

    Minor

    Started, per Fly.io

    Latest status Fly.io postedInvestigating. No resolution posted.

  • Delayed ingestion of app logs

    Minor

    Started, per Fly.io

    Latest status Fly.io postedInvestigating. No resolution posted.

  • Network outage in AMS region

    Critical

    Started, per Fly.io

    Closed in our record(28m)

    Fly.io’s post

  • State database issues in GRU

    Major

    Started, per Fly.io

    Closed in our record(2h 48m)

    Fly.io’s post

  • Private Networking issues (6PN)

    Major

    Started, per Fly.io

    Closed in our record(48m)

    Fly.io’s post

  • Partial Sprites outage

    Major

    Started, per Fly.io

    Closed in our record(7h 31m)

    Fly.io’s post

  • Elevated private networking errors

    Major

    Started, per Fly.io

    Closed in our record(37m)

    Fly.io’s post

  • Upstash unavailability in FRA region

    Major

    Started, per Fly.io

    Closed in our record(1h 27m)

    Fly.io’s post

  • IPv6 Networking Issues in DFW

    Major

    Started, per Fly.io

    Closed in our record(6h 1m)

    Fly.io’s post

  • Depot builder failures

    Minor

    Started, per Fly.io

    Closed in our record(1h 31m)

    Fly.io’s post

  • Network issues in US West Coast

    Minor

    Started, per Fly.io

    Closed in our record(57m)

    Fly.io’s post

  • Sprites API Partial Outage

    Minor

    Started, per Fly.io

    Closed in our record(1h 46m)

    Fly.io’s post

  • Upstream network issues

    Minor

    Started, per Fly.io

    Closed in our record(1h 42m)

    Fly.io’s post

  • API background job queue failure

    Major

    Started, per Fly.io

    Closed in our record(23m)

    Fly.io’s post

Your code, your dependencies

See which of your code paths call Fly.io

Connect GitHub or GitLab to find where your public or private repository uses Fly.io. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Fly.io status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · Fly.ioStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/fly-io?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Fly.io status badge"></iframe>

Frequently Asked Questions

Is Fly.io currently down?

Fly.io's latest recorded status is Partial Outage. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Fly.io last have an outage?

The most recent closed incident record began 19 days ago and spans 28 minutes. The vendor reported a complete outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Fly.io?

No. CheckUpstream checks Fly.io’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Fly.io in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Fly.io?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors