Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Cloudflare: vendor-reported minor incident on September 22 (tracked 3d 0h)

Sep 22, 07:44 PM → Sep 25, 07:46 PM · 3d 0h · medium

Cloudflare reported a minor-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 3d 0h, from Tue, 22 Sep 2026 19:44:34 GMT to Fri, 25 Sep 2026 19:46:24 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
3d 0h
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 22, 07:44 PM

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

  2. Sep 24, 07:41 AM

    Status updated: possible issue

  3. Sep 24, 06:05 PM

    Status updated: major issue

  4. Sep 24, 10:35 PM

    Status updated: possible issue

  5. Sep 24, 10:39 PM

    Status updated: major issue

  6. Sep 25, 12:02 AM

    Status updated: possible issue

  7. Sep 25, 12:14 AM

    Status updated: major issue

  8. Sep 25, 01:41 AM

    Status updated: possible issue

  9. Sep 25, 05:56 AM

    Status updated: major issue

  10. Sep 25, 06:00 AM

    Status updated: possible issue

  11. Sep 25, 06:06 AM

    Status updated: major issue

  12. Sep 25, 09:01 AM

    Status updated: possible issue

  13. Sep 25, 07:46 PM

    PulseWatch closed the incident

Official updates

  1. Sep 22, 07:44 PM

    Cloudflare 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