Flightcontrol incident

Network issues on newly-created machines

Resolved after 9 hours 14 minutes, affecting Customer Applications, on February 5, 2026.

monitoring Feb 06, 2026, 02:49 AM UTC

We have successfully run a fix to re-sync our global and regional state stores in order to bring machines back to a healthy state, and we're monitoring the situation to confirm that there are no more issues.

Started
Feb 05, 2026, 09:52 PM UTC
Resolved
Feb 06, 2026, 07:07 AM UTC
Duration
9h 14m
Detected by Pingoru
Feb 05, 2026, 09:52 PM UTC

Affected components

Customer Applications

Update timeline

  1. identified Feb 05, 2026, 09:52 PM UTC

    Machines created after the delayed machine registration incident (https://status.flyio.net/incidents/3npj6935byt4) may have incomplete networking configurations and could be unable to receive traffic. We've identified the issue and are deploying code fixes as well as updating created machines. This affects a small number of machines on all our regions.

  2. monitoring Feb 06, 2026, 02:49 AM UTC

    We have successfully run a fix to re-sync our global and regional state stores in order to bring machines back to a healthy state, and we're monitoring the situation to confirm that there are no more issues.

  3. resolved Feb 06, 2026, 07:07 AM UTC

    This issue is now resolved.

Your product runs on more than Flightcontrol

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →