Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 1 — 1h 32m disruption

May 1, 03:00 PM → May 1, 04:33 PM · 1h 32m · high

Cloudflare experienced a service disruption on May 1, 2026. This incident, which was detected via user reports, began at approximately 15:00 UTC and was resolved by 16:33 UTC.

Peak reports
10
in 15 min
Total reports
49
during the incident
Duration
1h 32m
tracked by PulseWatch

Impact

Users reported a high-severity service disruption affecting Cloudflare. The most frequently reported issues included websites being down, slow or unresponsive services, and API-related problems. A total of 49 user reports were received during the incident. No specific regional concentrations of impact were identified.

Top reported issues

  • Website down24
  • Slow / unresponsive21
  • API issues4

Incident timeline

  1. May 1, 03:00 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 04:30 PM

    Peak of 9 reports in 15 minutes (baseline 4.0)

  3. May 1, 04:33 PM

    Report volume returned to baseline — incident resolved

Official updates

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