Minor impactResolvedCloud

Fly.io incident: Elevated errors creating apps and managing secrets

Fly.io reported this minor-impact incident on its official status page on Oct 15, 2026, 09:30 UTC. It was resolved after 2h 4m.

Right now Fly.io is operational. Live Fly.io status →

🔔 Get alerted when Fly.io has issuesFree · email alerts · no credit card
Oct 15, 2026, 09:30 UTC
started
Oct 15, 2026, 11:33 UTC
resolved
2h 4m
duration
Minor
impact
  1. resolvedOct 15, 2026, 11:33 UTC

    Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.

  2. monitoringOct 15, 2026, 09:57 UTC

    We’ve applied a fix for the elevated errors affecting app creation and secrets management. Error rates and response times have returned to normal. We’re continuing to monitor to confirm the issue is fully resolved.

  3. investigatingOct 15, 2026, 09:30 UTC

    We’re seeing elevated error rates and slow responses for some operations that create or change data. Creating new apps, setting or removing secrets, and some app deletions are affected. You may see 500 or 503 errors from `flyctl`, the Machines API, or the dashboard. Apps and Machines that are already running are not affected. Starting, stopping and reading existing Machines are working normally. We’re investigating and will post another update within 30 minutes.

What APIStatus.watch saw

  • Oct 15, 2026, 09:34 UTCoperational → degraded
  • Oct 15, 2026, 11:34 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Fly.io have incidents?

Fly.io reported 27 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h. See Fly.io's uptime and incident history