Sprites API Partial Outage
Last updateresolvedSep 3 · 00:41 UTC
This incident has been resolved.
Reported by Fly.io on their status page.

checked Sep 11, 2026 3:07 PM UTC · Fly.io's official status page
Fly.io is up and running.
All components operational
Statusfield watches Fly.io alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
18 reports published by Fly.io in the last 30 days
When Fly.io breaks, it is typically resolved in 1h 33m — median across 39 resolved incidents over 90 days.
resolvedSep 3 · 00:41 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedSep 2 · 15:57 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedSep 2 · 07:44 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 31 · 15:30 UTC
A configuration update caused temporary failures for incoming HTTP/2 traffic for Fly Machines located on a subset of hosts for a few minutes. This incident has since been resolved. Managed Postgres depends on HTTP/2 and some control plane ops may have been affected as well. However, downstream Postgres connections were unlikely to have been affected by this since they do not use the HTTP2 handler.
Reported by Fly.io on their status page.
resolvedAug 31 · 08:10 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 30 · 22:45 UTC
We saw Sprite deletion jobs failing between 21:18 and 22:05 UTC. This issue has been resolved.
Reported by Fly.io on their status page.
resolvedAug 28 · 22:36 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 28 · 10:22 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 26 · 18:43 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 24 · 13:24 UTC
This is now resolved
Reported by Fly.io on their status page.
resolvedAug 23 · 02:10 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 20 · 19:30 UTC
A BGP configuration error caused our Anycast DNS to route to some nodes without the proper DNS infrastructure. The issue was temporary and was resolved as soon as we removed that node from BGP.
Reported by Fly.io on their status page.
resolvedAug 20 · 14:16 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 20 · 07:57 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 19 · 00:00 UTC
6PN networking issues between some machines in YYZ during a rollout which was rolled back once we noticed errors. During this time some machines were unable to talk to internal resources like other DBs, other apps or MPG clusters.
Reported by Fly.io on their status page.
resolvedAug 17 · 15:41 UTC
The capacity issue in the ARN region has been resolved.
Reported by Fly.io on their status page.
resolvedAug 14 · 20:33 UTC
This incident has been resolved.
Reported by Fly.io on their status page.
resolvedAug 13 · 19:41 UTC
This incident has been resolved.
Reported by Fly.io on their status page.