Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 1 — 2d 2h disruption

May 1, 09:06 PM → May 3, 11:19 PM · 2d 2h · high

On May 1, 2026, Cloudflare experienced a service disruption that was detected through user reports. The incident, which began at approximately 21:06 UTC, affected various services. The issue was fully resolved by May 3, 2026, at 23:19 UTC.

Peak reports
15
in 15 min
Total reports
1,000
during the incident
Duration
2d 2h
tracked by PulseWatch

Impact

During the Cloudflare service disruption, users reported a range of issues, primarily experiencing websites being down (796 reports). Other significant impacts included slow or unresponsive services (132 reports) and API issues (52 reports). A smaller number of users also reported login difficulties (20 reports). While no specific regional impacts were recorded, the widespread nature of the reports indicates a broad user-visible effect.

Top reported issues

  • Website down796
  • Slow / unresponsive132
  • API issues52
  • Login issues20

Incident timeline

  1. May 1, 09:06 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  3. May 3, 11:19 PM

    Report volume returned to baseline — incident resolved

Official updates

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