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 major incident on September 23 (tracked 6h 0m)

Sep 23, 06:21 AM → Sep 23, 12:21 PM · 6h 0m · high

Fly.io reported a major-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 6h 0m, from Wed, 23 Sep 2026 06:21:04 GMT to Wed, 23 Sep 2026 12:21:16 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
6h 0m
tracked by PulseWatch

Impact

During the 6-hour high-severity incident affecting Fly.io, service availability was impacted. This disruption was identified through automated monitoring and the vendor's status page. No user-reported data, such as specific affected regions or issue types, was collected for this incident.

Incident timeline

  1. Sep 23, 06:21 AM

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

  2. Sep 23, 06:21 AM

    Status updated: possible issue

  3. Sep 23, 12:21 PM

    PulseWatch closed the incident

Official updates

  1. Sep 23, 06:21 AM

    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: gemini-2.5-flash