Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 1 — 1h 27m disruption

May 1, 05:30 PM → May 1, 06:58 PM · 1h 27m · high

Cloudflare experienced a service disruption on May 1, 2026, which was detected through user reports. The incident began at 17:30 UTC and was resolved at 18:58 UTC.

Peak reports
20
in 15 min
Total reports
54
during the incident
Duration
1h 27m
tracked by PulseWatch

Impact

During the incident, users reported various issues with Cloudflare services. A total of 54 reports were received, with a peak of 20 reports within a 15-minute period. The most frequently reported issues included websites being down, slow or unresponsive service, and API-related problems. No specific regional impact was recorded.

Top reported issues

  • Website down24
  • Slow / unresponsive18
  • API issues12

Incident timeline

  1. May 1, 05:30 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 05:45 PM

    Peak of 13 reports in 15 minutes (baseline 4.0)

  3. May 1, 05:53 PM

    Status updated: possible issue

  4. May 1, 05:58 PM

    Status updated: possible issue

  5. May 1, 06:58 PM

    Report volume returned to baseline — incident resolved

Official updates

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