---
id: "INC-fly-01M6E41ER0BWGC0Z76XE8AEWVF"
kind: "incident"
aliases: []
title: "Fly.io: Elevated Machine start failures in ARN"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Fly.io", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["fly", "hosting", "incident", "ops", "vendor"]
not_affected_if: []
published_at: "2026-11-02T12:34:10+00:00"
first_seen_at: "2026-11-02T12:35:41+00:00"
updated_at: "2026-11-02T13:36:53+00:00"
sources: [{"source": "statuspage", "url": "https://status.flyio.net/incidents/01M6E41ER0BWGC0Z76XE8AEWVF", "first_seen_at": "2026-11-02T12:35:41+00:00"}]
---

# Fly.io: Elevated Machine start failures in ARN

## Affected

- vendor:Fly.io affected ? fixed ?

## Timeline

- 2026-11-02T12:35:41+00:00 statuspage https://status.flyio.net/incidents/01M6E41ER0BWGC0Z76XE8AEWVF

## From the sources

We're currently investigating an elevated level of machine start failures. Workaround in the meantime would be to [replace affected machines ](https://docs.fly.io/apps/trouble-host-unavailable#apps-with-one-machine-and-no-volumes)with a new one: `fly machine clone `

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_