Elevated GraphQL API errors
Mar 3, 20:18 UTCMar 3, 21:15 UTC
Duration
57m
Impact
Major
Root cause
Not disclosed
Fly.io, 90 days
51 incidents
Affected
Not listed by the vendor.
Final update
This incident was caused by a failed Redis node that powers our GraphQL API. We were able to recreate the Redis node and restore service. We are still investigating the root cause of the failure. In the mean time, all API endpoints now appear to be stable and errors have dropped to baseline level.
Timeline
- Resolved · Mar 3, 21:15 UTC
This incident was caused by a failed Redis node that powers our GraphQL API. We were able to recreate the Redis node and restore service. We are still investigating the root cause of the failure. In the mean time, all API endpoints now appear to be stable and errors have dropped to baseline level.
More from Fly.io
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| 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 |
| Sep 1504:08 UTC | Depot builder failures | minor | 1h 25m |
| Sep 1221:22 UTC | Network issues in US West Coast | minor | 50m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.