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
51 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 history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2318:44 UTC | Partial Sprites outage | major | 7h 28m |
| Sep 2314:47 UTC | Elevated private networking errors | major | 36m |
| Sep 2312:42 UTC | Upstash unavailability in FRA region | major | 1h 22m |
| Sep 2306:18 UTC | IPv6 Networking Issues in DFW | major | 5h 57m |
| Sep 1504:08 UTC | Depot builder failures | minor | 1h 25m |
| Sep 1221:22 UTC | Network issues in US West Coast | minor | 50m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.