Changes / Fly.io / Partial Sprites outage
Fly.io: Major incident: Partial Sprites outage
Summary
Fly.io reported a major partial Sprites outage with intermittent API failures near SJC, later extending to other regions and affecting creating, connecting to, or managing Sprites. It ran from 2026-09-23 18:44 UTC to 2026-09-24 02:12 UTC (7 h 28 min) and was resolved after mitigations and potential fixes were deployed.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
Major incidentLabel: outage (model (Jev), 52%)Changed Detected Source: status.flyio.net (opens in new tab)
What changed
Before: not present
After: Partial Sprites outage
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-23 18:44 UTC
Before: not present
After: 2026-09-24 02:12 UTC
Before: not present
After: We are investigating intermittent API failures for users connecting near SJC.
Before: not present
After: The issue has been identified and we are rolling out mitigations.
Before: not present
After: This issue is now occurring on regions other than SJC. We are still working on a fix.
Before: not present
After: We have deployed another potential fix and are monitoring results.
Before: not present
After: Sprites API performance has largely recovered and most users should no longer see errors creating, connecting to, or managing Sprites. We're still seeing a small number of intermittent errors and are investigating them before resolving this incident.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Partial Sprites outage (this change) Fly.io reported a major partial Sprites outage with intermittent API failures near SJC, later extending to other regions and affecting creating, connecting to, or managing Sprites. It ran from 2026-09-23 18:44 UTC to 2026-09-24 02:12 UTC (7 h 28 min) and was resolved after mitigations and potential fixes were deployed. | Major incident |