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
53 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 historyIPv6 egress issues on a subset of IAD hostslasted 23mEmergency network maintenance on a subset of hosts in ORDlasted 14mElevated Machine start failures in ARNlasted 1h 1mEmergency maintenance in IADlasted 38mOutbound IPv4 connectivity failures in ARN, JNB, and GRUlasted 2h 10mSlow image pulls delaying Machine starts in IADlasted 1h 28m