Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 4 "," 3h 48m disruption

May 4, 04:01 AM → May 4, 07:49 AM · 3h 48m · high

Cloudflare experienced a service disruption on May 4, 2026, which was detected through user reports. The incident began at approximately 04:01 UTC and was fully resolved by 07:49 UTC on the same day.

Peak reports
13
in 15 min
Total reports
104
during the incident
Duration
3h 48m
tracked by PulseWatch

Impact

The service disruption was characterized by a high severity, with a total of 104 user reports received during the incident. The most frequently reported issues included websites being down, accounting for 64 reports, and slow or unresponsive service, with 40 reports. While no specific top impacted regions were recorded, the widespread nature of the reports indicates a broad impact on users attempting to access services relying on Cloudflare. The incident was initially detected through these user reports.

Top reported issues

  • Website down64
  • Slow / unresponsive40

Incident timeline

  1. May 4, 04:01 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 04:15 AM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 4, 07:49 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 04:01 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