Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 1 — 3h 42m disruption

May 1, 04:16 PM → May 1, 07:58 PM · 3h 42m · high

A service disruption affecting Cloudflare was detected through user reports starting on May 1, 2026, at 16:16 UTC. Users experienced issues across various services. The incident was resolved on May 1, 2026, at 19:58 UTC.

Peak reports
22
in 15 min
Total reports
134
during the incident
Duration
3h 42m
tracked by PulseWatch

Impact

During the incident, a total of 134 user reports were received, with a peak of 22 reports within a 15-minute period. The most frequently reported issues included websites being down (60 reports), slow or unresponsive service (54 reports), and API-related problems (20 reports). Specific regional impacts were not recorded. These reports indicated a high severity disruption to Cloudflare services.

Top reported issues

  • Website down60
  • Slow / unresponsive54
  • API issues20

Incident timeline

  1. May 1, 04:16 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 04:30 PM

    Peak of 13 reports in 15 minutes (baseline 4.0)

  3. May 1, 07:58 PM

    Report volume returned to baseline — incident resolved

Official updates

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