Increased app-not-found errors

Timeline

1. 02:50 UTC Fly.io status page · Reported Increased app-not-found errors
2. 02:50 UTC Fly.io status page · Investigating We are currently investigating app-not-found errors returned by Machines API calls made shortly after creating new applications.
3. 03:50 UTC Fly.io status page · Identified 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.
4. 04:58 UTC Fly.io status page · Identified We’ve applied a mitigation to reduce the impact from Corrosion batch insertion retries and are continuing to monitor while affected nodes catch up.
5. 06:03 UTC Fly.io status page · Identified 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.
6. 06:42 UTC Fly.io status page · Monitoring A fix has been implemented and we are monitoring the results
7. 07:10 UTC Fly.io status page · Resolved This incident has been resolved.