Fly.io incident

Elevated GraphQL API errors

Major Resolved View vendor source →
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.

Looking to track Fly.io downtime and outages?

Pingoru polls Fly.io's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Fly.io reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Fly.io alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Fly.io for free

5 free monitors · No credit card required