Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Fly.io

flyctl deploy creating new app instances

Resolved Minor
April 28, 2026 - Started about 6 hours ago - Lasted about 1 hour
Official incident page

Incident Report

Summary AI Generated

Fly.io experienced a deployment issue where `fly deploy` commands were creating new machine instances instead of updating existing ones, causing applications to enter a mixed state. The problem affected the Deployments component and lasted 51 minutes before being resolved. Users could work around the issue by either removing the "processes = [ "app" ]" line from their fly.toml configuration or downgrading flyctl to version 0.4.40.

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. Another workaround is to downgrade flyctl to 0.4.40 - this should resolve the issue in the meantime.
Components affected
Fly.io Deployments

Trusted by 1,000+ teams

Never miss outages in third-party dependencies

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED about 5 hours ago - at 04/29/2026 12:40AM

This incident has been resolved.

MONITORING about 5 hours ago - at 04/29/2026 12:31AM

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

IDENTIFIED about 6 hours ago - at 04/29/2026 12:07AM

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

INVESTIGATING about 6 hours ago - at 04/28/2026 11:50PM

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. Another workaround is to downgrade flyctl to 0.4.40 - this should resolve the issue in the meantime.

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook