Fly.io incident

Certificates issues affecting API and proxy

Notice Resolved View vendor source →
Started
Mar 03, 2026, 02:05 AM UTC
Resolved
Mar 03, 2026, 12:54 AM UTC
Duration
Detected by Pingoru
Mar 03, 2026, 02:05 AM UTC

Update timeline

  1. resolved Mar 03, 2026, 02:05 AM UTC

    Between 19:54 and 20:06 UTC, our Vault cluster serving app certificates was unavailable. This caused various API requests to fail, mainly operations on certificates but also app creates and IP assignments. As the failure mode was Vault requests hanging rather than failing immediately, TLS requests through fly-proxy for domains where the certificate was not cached on the local node remained open for a long time while proxy attempted to fetch the certificate; this caused some connections to fail as too many connection slots were taken up by requests waiting on Vault. The root cause of this incident was a partially completed update to the Vault cluster. We will be implementing safeguards in the proxy for this failure mode, as well as improving certificate storage longer-term.

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