Skip to content
Back to Cloudflare CDNIncident Postmortem
Cloudflare CDN logo

Cloudflare CDN

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare CDN outage on May 1 — 1h 3m disruption

May 1, 10:44 AM → May 1, 11:47 AM · 1h 3m · high

On May 1, 2026, Cloudflare CDN experienced a service disruption, detected through user reports. The incident began at 10:44 UTC and was resolved at 11:47 UTC, resulting in a 1 hour and 3 minute disruption.

Peak reports
20
in 15 min
Total reports
55
during the incident
Duration
1h 3m
tracked by PulseWatch

Impact

The service disruption was identified through user reports, indicating a high severity incident. A peak of 20 reports was received within a 15-minute period, totaling 55 reports throughout the outage. Users primarily reported 'Cloud provider issues' and 'Website down'. No specific regional impact was recorded during this time.

Top reported issues

  • Cloud provider issues39
  • Website down16

Incident timeline

  1. May 1, 10:44 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 10:45 AM

    Peak of 4 reports in 15 minutes (baseline 10.0)

  3. May 1, 11:47 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 1, 10:44 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