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 — 5h 20m disruption

May 4, 09:58 PM → May 5, 03:19 AM · 5h 20m · medium

An incident affecting Cloudflare CDN services was detected on May 4, 2026. This disruption was identified through user reports and resolved on May 5, 2026.

Peak reports
19
in 15 min
Total reports
287
during the incident
Duration
5h 20m
tracked by PulseWatch

Impact

Users reported issues with Cloudflare CDN services during the incident. A total of 287 reports were received, with the most common issue types being "Cloud provider issues" and "Website down." No specific regional impact was observed or recorded. These reports indicated a general disruption to services relying on Cloudflare CDN.

Top reported issues

  • Cloud provider issues195
  • Website down92

Incident timeline

  1. May 4, 09:58 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 5, 12:45 AM

    Peak of 14 reports in 15 minutes (baseline 10.0)

  3. May 5, 12:53 AM

    Status updated: possible issue

  4. May 5, 12:58 AM

    Status updated: possible issue

  5. May 5, 03:19 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 09:58 PM

    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