Flightcontrol incident

Machine Creates Failing in ORD Region

Major Resolved View vendor source →
Started
Mar 26, 2026, 03:21 PM UTC
Resolved
Mar 26, 2026, 05:54 PM UTC
Duration
2h 33m
Detected by Pingoru
Mar 26, 2026, 03:21 PM UTC

Affected components

ORD - Chicago, Illinois (US)

Update timeline

  1. investigating Mar 26, 2026, 03:21 PM UTC

    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.

  2. investigating Mar 26, 2026, 04:08 PM UTC

    We are continuing to investigate this issue. We are seeing 408 errors decreasing in ORD, though still above baseline.

  3. identified Mar 26, 2026, 04:50 PM UTC

    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.

  4. monitoring Mar 26, 2026, 05:28 PM UTC

    We've implemented a fix and have seen error rates for machine creates in ORD drop off. We're continuing to monitor the results.

  5. resolved Mar 26, 2026, 05:54 PM UTC

    This incident has been resolved.

Looking to track Flightcontrol downtime and outages?

Pingoru polls Flightcontrol's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Flightcontrol reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Flightcontrol alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Flightcontrol for free

5 free monitors · No credit card required