Skip to content
Back to Cloudflare CDNIncident Postmortem
Cloudflare CDN logo

Cloudflare CDN

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare CDN outage on May 4 — 2h 17m disruption

May 4, 08:58 AM → May 4, 11:15 AM · 2h 17m · high

On May 4, 2026, Cloudflare CDN experienced a service disruption, which was first detected through user reports. The incident began at 08:58 UTC and was resolved at 11:15 UTC, lasting 2 hours and 17 minutes.

Peak reports
20
in 15 min
Total reports
124
during the incident
Duration
2h 17m
tracked by PulseWatch

Impact

The disruption was initially identified through user reports, with a total of 124 reports received during the incident. At its peak, 20 reports were received within a 15-minute period. The most frequently reported issues included 'Cloud provider issues' and 'Website down'. No specific regional impact was recorded.

Top reported issues

  • Cloud provider issues84
  • Website down40

Incident timeline

  1. May 4, 08:58 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 09:30 AM

    Peak of 17 reports in 15 minutes (baseline 10.0)

  3. May 4, 11:15 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 08:58 AM

    Cloudflare CDN 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