Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 2 2h 0m disruption

May 2, 02:02 AM → May 2, 04:03 AM · 2h 0m · high

A service disruption affecting Cloudflare was detected on May 2, 2026, initially through user reports. The incident, which began at 02:02 UTC, was resolved at 04:03 UTC on the same day.

Peak reports
6
in 15 min
Total reports
56
during the incident
Duration
2h 0m
tracked by PulseWatch

Impact

Users reported experiencing issues with Cloudflare services, primarily manifesting as website downtime and API connectivity problems. A total of 56 user reports were received during the incident, with 'Website down' being the most frequently reported issue type (32 reports), followed by 'API issues' (24 reports). No specific regional impact was recorded.

Top reported issues

  • Website down32
  • API issues24

Incident timeline

  1. May 2, 02:02 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 2, 02:15 AM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 2, 04:03 AM

    Report volume returned to baseline — incident resolved

Official updates

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