Flightcontrol incident

flyctl deploy creating new app instances

Minor Resolved View vendor source →
Started
Apr 28, 2026, 11:50 PM UTC
Resolved
Apr 29, 2026, 12:40 AM UTC
Duration
49m
Detected by Pingoru
Apr 28, 2026, 11:50 PM UTC

Affected components

Deployments

Update timeline

  1. investigating Apr 28, 2026, 11:50 PM UTC

    We're investigating an issue where fly deploy is creating new Fly machine instances rather than updating existing ones, leading to apps with a mixed state. We're currently investigating the issue. As a workaround, please try removing the "processes = [ "app" ]" line from your fly.toml configuration file and redeploying - this should resolve the issue in the meantime.

  2. identified Apr 29, 2026, 12:07 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 29, 2026, 12:31 AM UTC

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

  4. resolved Apr 29, 2026, 12:40 AM 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