Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 4 — 1h 3m disruption

May 4, 01:46 PM → May 4, 02:49 PM · 1h 3m · high

On May 4, 2026, Cloudflare experienced a high-severity service disruption. This incident was detected through user reports and lasted for 1 hour and 3 minutes. Service was fully restored at 14:49 UTC.

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

Impact

Users reported experiencing issues with Cloudflare services, leading to a total of 28 reports during the incident. The most frequently reported issues included websites being down, accounting for 20 reports, and slow or unresponsive service, with 8 reports. No specific top impacted regions were recorded during this period. The disruption was primarily identified through these user-submitted reports.

Top reported issues

  • Website down20
  • Slow / unresponsive8

Incident timeline

  1. May 4, 01:46 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 02:00 PM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 4, 02:13 PM

    Status updated: major issue

  4. May 4, 02:23 PM

    Status updated: major issue

  5. May 4, 02:28 PM

    Status updated: major issue

  6. May 4, 02:49 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 01:46 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