Fly.io incident

Network issues on newly-created machines

Minor Resolved View vendor source →
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.

Looking to track Fly.io downtime and outages?

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

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

5 free monitors · No credit card required