Fly.io Investigating App-Not-Found Errors After Application Creation

The platform is investigating increased app-not-found errors returned by its Machines API shortly after new applications are created.

By The Downtime · Aug 9, 2026 · 3:00 AM ·Updated 1 week ago

Fly.io is currently investigating a major incident involving app-not-found errors returned by Machines API calls made shortly after creating new applications.

Fly.io is a cloud platform that enables developers to deploy and run applications globally across multiple regions.

The company first reported the issue as it began investigating the increased error rates affecting the API. No additional timeline updates have been provided at this time.

This is a developing story and will be updated as more information becomes available.

🕒 Live updates (6)

resolved Aug 9, 7:10 AM

This incident has been resolved.

monitoring Aug 9, 6:42 AM

A fix has been implemented and we are monitoring the results

identified Aug 9, 6:03 AM

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.

identified Aug 9, 4:58 AM

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, 3:50 AM

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.

investigating Aug 9, 2:50 AM

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

📎 Sources

Fly.io status ↗

Outage details are aggregated from official provider status pages. The Downtime reports them as a public service and is not affiliated with the providers named.