Changes / Fly.io / Partial outage in AMS
Fly.io: Critical incident: Partial outage in AMS
Summary
Fly.io reported a critical partial outage in AMS starting 2026-10-03 08:01 UTC, lasting 56 min and resolved at 2026-10-03 08:57 UTC. Offline hosts made some machines unavailable and blocked Managed Postgres v1 and v2 control-plane operations; some MPGv1 clusters later experienced possible degradation. Hosts and all impacted services recovered.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
Major incidentLabel: outage (model (Jev), 99%)Changed Detected Source: status.flyio.net (opens in new tab)
What changed
Before: not present
After: Partial outage in AMS
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-10-03 08:01 UTC
Before: not present
After: 2026-10-03 08:57 UTC
Before: not present
After: Some of our hosts are offline in AMS. Control plane for Managed Postgres v1 and v2 in AMS is unavailable as a result of this. MPG clusters should remain online but any control plane ops will fail. Some machines in AMS are also unavailable.
Before: not present
After: Those hosts are coming back online after a brief interruption. We are assessing the impact on MPG.
Before: not present
After: All hosts are back online. MPGv2 control plane is fully operational now. Some MPGv1 clusters in AMS might be degraded while MPGv1's control plane recovers.
Before: not present
After: All MPG clusters have recovered. We are monitoring for additional impact.
Before: not present
After: All impacted services are operational now.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Partial outage in AMS (this change) Fly.io reported a critical partial outage in AMS starting 2026-10-03 08:01 UTC, lasting 56 min and resolved at 2026-10-03 08:57 UTC. Offline hosts made some machines unavailable and blocked Managed Postgres v1 and v2 control-plane operations; some MPGv1 clusters later experienced possible degradation. Hosts and all impacted services recovered. | Major incident |