← Back to Fly.io History
major✓ Resolved
Increased app-not-found errors
Status
resolved
Duration
4h 25m
Updates
5
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedSun, Aug 9, 2026, 07:15 AM
This incident has been resolved.
monitoringSun, Aug 9, 2026, 06:42 AM
A fix has been implemented and we are monitoring the results
identifiedSun, Aug 9, 2026, 06: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.
identifiedSun, Aug 9, 2026, 04: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.
identifiedSun, Aug 9, 2026, 03: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.
investigatingSun, Aug 9, 2026, 02:50 AM
We are currently investigating app-not-found errors returned by Machines API calls made shortly after creating new applications.
📊 TECHNICAL DETAILS
Internal ID
ddec63b7-ea05-405e-917d-fa74735f2260
External ID
smh0bkbsqnr8
🕐 Started
Sun, Aug 9, 2026, 02:50 AM
🔄 Last Updated
Sun, Aug 9, 2026, 07:15 AM
✓ Resolved
Sun, Aug 9, 2026, 07:15 AM
MAJOR
Impact Level
4h 25m
Total Duration
5
Status Updates
Affected Components
Machines API
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed