Increased app-not-found errors
Aug 9, 02:50 UTCAug 9, 07:10 UTC
Duration
4h 20m
Impact
Major
Root cause
Not disclosed
Fly.io, 90 days
53 incidents
Affected
Machines API
Final update
This incident has been resolved.
Timeline
- Resolved · Aug 9, 07:10 UTC
This incident has been resolved.
- Monitoring · Aug 9, 06:42 UTC
A fix has been implemented and we are monitoring the results
- Identified · Aug 9, 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.
- Identified · Aug 9, 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.
- Identified · Aug 9, 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.
- Investigating · Aug 9, 02:50 UTC
We are currently investigating app-not-found errors returned by Machines API calls made shortly after creating new applications.
More from Fly.io
Full historyIPv6 egress issues on a subset of IAD hostslasted 23mEmergency network maintenance on a subset of hosts in ORDlasted 14mElevated Machine start failures in ARNlasted 1h 1mEmergency maintenance in IADlasted 38mOutbound IPv4 connectivity failures in ARN, JNB, and GRUlasted 2h 10mSlow image pulls delaying Machine starts in IADlasted 1h 28m