Fly.io incident

Elevated GraphQL API errors

Resolved after 57 minutes, affecting Dashboard and Deployments, on March 3, 2026.

resolved Mar 03, 2026, 09:15 PM 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.

Started
Mar 03, 2026, 08:18 PM UTC
Resolved
Mar 03, 2026, 09:15 PM UTC
Duration
57m
Detected by Pingoru
Mar 03, 2026, 08:18 PM UTC

Affected components

DashboardDeployments

Update timeline

  1. investigating Mar 03, 2026, 08:18 PM UTC

    We're investigating elevated GraphQL errors that affect some API endpoints.

  2. monitoring Mar 03, 2026, 08:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 03, 2026, 09:15 PM 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.

Your product runs on more than Fly.io

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →