Flightcontrol incident

Machines failing to start in DFW

Major Resolved View vendor source →
Started
Mar 18, 2026, 09:58 AM UTC
Resolved
Mar 18, 2026, 06:53 PM UTC
Duration
8h 55m
Detected by Pingoru
Mar 18, 2026, 09:58 AM UTC

Update timeline

  1. investigating Mar 18, 2026, 09:58 AM UTC

    We are investigating reports of machines failing to start in the DFW (Dallas) region with "insufficient memory" errors. This may cause deployment failures for applications running in DFW. Our team is actively working to restore full capacity in the region. If you are affected, deploying to an alternate region may serve as a temporary workaround. We will provide updates as the situation progresses.

  2. identified Mar 18, 2026, 11:44 AM UTC

    The team is currently rolling out additional capacity in DFW which should help ease Machine start failures across the region.

  3. monitoring Mar 18, 2026, 12:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 18, 2026, 06:53 PM UTC

    This incident has been resolved. Machine creates in DFW continue to work normally.

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