Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 2 A 3h 43m disruption

May 2, 12:30 AM → May 2, 04:13 AM · 3h 43m · high

Cloudflare experienced a service disruption on May 2, 2026, which was detected through user reports. The incident began at 00:30:09Z and was resolved at 04:13:18.999Z.

Peak reports
12
in 15 min
Total reports
112
during the incident
Duration
3h 43m
tracked by PulseWatch

Impact

During the incident, a total of 112 user reports were received, with a peak of 12 reports within a 15-minute period. Users primarily reported issues such as websites being down, API functionality problems, and slow or unresponsive service. No specific top impacted regions were recorded during this disruption.

Top reported issues

  • Website down60
  • API issues28
  • Slow / unresponsive24

Incident timeline

  1. May 2, 12:30 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 2, 12:45 AM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 2, 04:13 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 12:30 AM

    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