← Back to Fly.io History
major✓ Resolved

Machine Creates Failing in ORD Region

Fly.io•Thu, Mar 26, 2026, 03:21 PM
Status
resolved
Duration
2h 33m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedThu, Mar 26, 2026, 05:55 PM
This incident has been resolved.
monitoringThu, Mar 26, 2026, 05:28 PM
We've implemented a fix and have seen error rates for machine creates in ORD drop off. We're continuing to monitor the results.
identifiedThu, Mar 26, 2026, 04:50 PM
We've identified the cause of this increased failure rate and a fix is in progress. We are seeing most creates in ORD succeed at this time, though failure rate is still above baseline.
investigatingThu, Mar 26, 2026, 04:08 PM
We are continuing to investigate this issue. We are seeing 408 errors decreasing in ORD, though still above baseline.
investigatingThu, Mar 26, 2026, 03:21 PM
We are currently investigating elevated errors creating machines in the ORD (Chicago, Illinois) region. Users may see `failed to launch VM: request returned non-2xx status: 408` errors when creating, updating, or scaling machines in ORD. Existing, already running machines in the ORD region continue to run as normal.

📊 TECHNICAL DETAILS

Internal ID
0aa8d40f-a6e3-417e-8bff-a68e1d6299f9
External ID
mrl4dfscjp1f
🕐 Started
Thu, Mar 26, 2026, 03:21 PM
🔄 Last Updated
Thu, Mar 26, 2026, 05:55 PM
✓ Resolved
Thu, Mar 26, 2026, 05:55 PM
MAJOR
Impact Level
2h 33m
Total Duration
4
Status Updates
Affected Components
ORD - Chicago, Illinois (US)
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