Increased app-not-found errors

What to do

• Check whether you use Fly.io Machines API. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 20m it lasted.

  Anything that failed between 2026-08-09 02:50 UTC and 2026-08-09 07:10 UTC may need a replay.

• Subscribe to Fly.io's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=fly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Fly.io 6

1. investigatingAug 9, 2026, 2:50 AM UTC

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

   provider

2. identifiedAug 9, 2026, 3:50 AM 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.

   provider

3. identifiedAug 9, 2026, 4:58 AM 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.

   provider

4. identifiedAug 9, 2026, 6:03 AM 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.

   provider

5. monitoringAug 9, 2026, 6:42 AM UTC

   A fix has been implemented and we are monitoring the results

   provider

6. resolvedAug 9, 2026, 7:10 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.