Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 5 A 48-minute disruption

May 5, 02:00 PM → May 5, 02:49 PM · 48 minutes · high

A service disruption affecting Cloudflare was detected, initially identified through user reports. The incident lasted approximately 48 minutes. Service was fully restored at 2:49 PM UTC on May 5, 2026.

Peak reports
6
in 15 min
Total reports
20
during the incident
Duration
48 minutes
tracked by PulseWatch

Impact

Users primarily reported issues with websites being down, accounting for 16 reports, and slow or unresponsive performance, which made up 4 reports. The disruption was initially identified through user reports, with a total of 20 reports received during the incident. No specific top impacted regions were recorded during this period.

Top reported issues

  • Website down16
  • Slow / unresponsive4

Incident timeline

  1. May 5, 02:00 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 5, 02:15 PM

    Peak of 4 reports in 15 minutes (baseline 1.5)

  3. May 5, 02:49 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 5, 02:00 PM

    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