Skip to content
Back to Cloudflare CDNIncident Postmortem
Cloudflare CDN logo

Cloudflare CDN

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare CDN outage on April 30 — 12h 18m disruption

Apr 30, 10:29 PM → May 1, 10:47 AM · 12h 18m · high

A service disruption affecting Cloudflare CDN was detected through user reports starting on April 30, 2026. Users experienced issues with content delivery. The incident was resolved on May 1, 2026.

Peak reports
16
in 15 min
Total reports
550
during the incident
Duration
12h 18m
tracked by PulseWatch

Impact

During the incident, a total of 550 user reports were received over a period of 12 hours and 18 minutes. The most frequently reported issue types included 'Cloud provider issues' and 'Website down'. No specific regional concentrations of impact were recorded.

Top reported issues

  • Cloud provider issues342
  • Website down208

Incident timeline

  1. Apr 30, 10:29 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 09:30 AM

    Peak of 8 reports in 15 minutes (baseline 7.0)

  3. May 1, 10:47 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. Apr 30, 10:29 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