Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 5 — 1h 48m disruption

May 5, 09:30 AM → May 5, 11:19 AM · 1h 48m · high

A high-severity incident impacted Cloudflare services on May 5, 2026. The issue began at 09:30:45 UTC and was fully resolved by 11:19:29 UTC, lasting 1 hour and 48 minutes. This incident was detected via user reports.

Peak reports
10
in 15 min
Total reports
52
during the incident
Duration
1h 48m
tracked by PulseWatch

Impact

Users reported issues with website accessibility and performance, with the primary reported problems being 'Website down' and 'Slow / unresponsive'. A total of 52 user reports were received during the incident, with a peak of 10 reports within a 15-minute window. No specific regions were identified as being disproportionately impacted.

Top reported issues

  • Website down32
  • Slow / unresponsive20

Incident timeline

  1. May 5, 09:30 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 5, 09:45 AM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 5, 10:23 AM

    Status updated: major issue

  4. May 5, 10:28 AM

    Status updated: major issue

  5. May 5, 10:38 AM

    Status updated: major issue

  6. May 5, 10:43 AM

    Status updated: major issue

  7. May 5, 10:53 AM

    Status updated: major issue

  8. May 5, 10:58 AM

    Status updated: major issue

  9. May 5, 11:19 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 5, 09:30 AM

    Cloudflare status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash-lite