Registry performance issues
Jul 9, 15:33 UTCJul 9, 16:04 UTC
Duration
31m
Impact
Minor
Root cause
Not disclosed
Fly.io, 90 days
52 incidents
Affected
Deployments
Final update
This incident has been resolved.
Timeline
- Resolved · Jul 9, 16:04 UTC
This incident has been resolved.
- Monitoring · Jul 9, 15:55 UTC
A fix has been implemented and we are monitoring the results.
- Identified · Jul 9, 15:33 UTC
The fly.io registry is currently experiencing capacity constraints that reduced performance and may lead to temporary high latency or failed pushes. We are currently working to add capacity and restore service.
More from Fly.io
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2416:31 UTC | State database issues in GRU | major | 2h 40m |
| Sep 2414:51 UTC | Private Networking issues (6PN) | major | 46m |
| Sep 2318:44 UTC | Partial Sprites outage | major | 7h 28m |
| Sep 2314:47 UTC | Elevated private networking errors | major | 36m |
| Sep 2312:42 UTC | Upstash unavailability in FRA region | major | 1h 22m |
| Sep 2306:18 UTC | IPv6 Networking Issues in DFW | major | 5h 57m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.