Companies / Fly.io / incidents

Fly.io: Increased app-not-found errors

Affected components: Machines API

Timeline of updates

1. investigating2026-08-09 02:50 UTC

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

2. identified2026-08-09 03:50 UTC

   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.

3. identified2026-08-09 04:58 UTC

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

4. identified2026-08-09 06:03 UTC

   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.

5. monitoring2026-08-09 06:42 UTC

   A fix has been implemented and we are monitoring the results

6. resolved2026-08-09 07:10 UTC

   This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on status.flyio.net (opens in new tab). Fly.io profile · Recent Fly.io incidents · Markdown · JSON