Flightcontrol incident

Increased app-not-found errors

Major Resolved View vendor source →

Flightcontrol experienced a major incident on August 9, 2026 affecting Machines API, lasting 4h 20m. The incident has been resolved; the full update timeline is below.

Started
Aug 09, 2026, 02:50 AM UTC
Resolved
Aug 09, 2026, 07:10 AM UTC
Duration
4h 20m
Detected by Pingoru
Aug 09, 2026, 02:50 AM UTC

Affected components

Machines API

Update timeline

  1. investigating Aug 09, 2026, 02:50 AM UTC

    We are currently investigating app-not-found errors returned by Machines API calls made shortly after creating new applications.

  2. identified Aug 09, 2026, 03:50 AM 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.

  3. identified Aug 09, 2026, 04:58 AM 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.

  4. identified Aug 09, 2026, 06:03 AM 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.

  5. monitoring Aug 09, 2026, 06:42 AM UTC

    A fix has been implemented and we are monitoring the results

  6. resolved Aug 09, 2026, 07:10 AM UTC

    This incident has been resolved.