Fly.io Status · History · Incident #6297

RESOLVED

Increased app-not-found errors

Major · Started Aug 9, 2026 · 2:50 AM

  • Duration

    4h 20m

  • Severity

    Major

  • Detection lead

  • User reports

Summary

Increased app-not-found errors

This incident has been resolved.


  • Started

    Aug 9, 2026 · 2:50 AM

  • Resolved

    Aug 9, 2026 · 7:10 AM

  • Duration

    4h 20m

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Aug 9 · 2:50 AM Fly.io

    We are currently investigating app-not-found errors returned by Machines API calls made shortly after creating new applications.

  • Identified

    Aug 9 · 3:50 AM Fly.io

    We have identified the issue as failed insertions in a subset of Corrosion batches. These failures trigger retries, which can cause timeouts for other batches.

  • Identified

    Aug 9 · 4:58 AM Fly.io

    We’ve applied a mitigation to reduce the impact from Corrosion batch insertion retries and are continuing to monitor while affected nodes catch up.

  • Identified

    Aug 9 · 6:03 AM Fly.io

    We’ve deployed an additional mitigation to further reduce Corrosion retry pressure and are seeing improvement; we’re continuing to monitor while remaining affected nodes catch up.

  • Monitoring

    Aug 9 · 6:42 AM Fly.io

    A fix has been implemented and we are monitoring the results

  • Resolved

    Aug 9 · 7:10 AM Fly.io

    This incident has been resolved.

Get alerted before the next Fly.io outage.

Pulsetic catches degradations minutes before vendors acknowledge them.