Skip to content
OutageDeck

Incident detail

Increased app-not-found errors

Resolved incidentMajor1 affected service

Timeline window

to

Outage alerts

Get alerted the next time Fly.io breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Fly.io alerts work

Timeline

Incident updates

Every update Fly.io posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

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

  2. 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.

  3. 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.

  4. 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.

  5. Monitoring

    A fix has been implemented and we are monitoring the results

  6. Resolved

    This incident has been resolved.

Keep exploring

More from Fly.io

Neighboring incidents on Fly.io's timeline and the rest of their record on OutageDeck.

← Older incident

MPG IAD data plane degraded for new clusters

All Fly.io incidentsFly.io live status