Skip to content
Back to Fly.ioIncident Postmortem
Fly.io logo

Fly.io

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Fly.io: vendor-reported critical incident on September 26 (tracked 26 minutes)

Sep 26, 07:51 PM → Sep 26, 08:17 PM · 26 minutes · high

Fly.io reported a critical-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 26 minutes, from Sat, 26 Sep 2026 19:51:20 GMT to Sat, 26 Sep 2026 20:17:37 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
26 minutes
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 26, 07:51 PM

    The vendor reported a critical-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 26, 07:51 PM

    Status updated: possible issue

  3. Sep 26, 08:17 PM

    PulseWatch closed the incident

Official updates

  1. Sep 26, 07:51 PM

    Fly.io reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: fallback