Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 2  1d 5h disruption

May 2, 03:24 PM → May 3, 09:04 PM · 1d 5h · high

A significant service disruption affecting Cloudflare was detected on May 2, 2026, primarily through user reports. The incident, which lasted approximately 1 day and 5 hours, impacted various services relying on Cloudflare infrastructure. Normal service was fully restored on May 3, 2026, at 21:04 UTC.

Peak reports
13
in 15 min
Total reports
546
during the incident
Duration
1d 5h
tracked by PulseWatch

Impact

Users reported a widespread disruption to services relying on Cloudflare, with a total of 546 reports received during the incident. The most frequently reported issues included websites being down, accounting for 482 reports. Additionally, users experienced slow or unresponsive services (44 reports) and login difficulties (20 reports). While no specific regional impact was recorded, the nature of the reports suggests a broad impact across various online services. This incident was initially detected and tracked based on these user-submitted reports.

Top reported issues

  • Website down482
  • Slow / unresponsive44
  • Login issues20

Incident timeline

  1. May 2, 03:24 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 2, 03:53 PM

    Status updated: major issue

  3. May 2, 03:58 PM

    Status updated: major issue

  4. May 2, 04:08 PM

    Status updated: major issue

  5. May 2, 04:13 PM

    Status updated: major issue

  6. May 2, 07:53 PM

    Status updated: possible issue

  7. May 2, 07:58 PM

    Status updated: possible issue

  8. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  9. May 3, 11:38 AM

    Status updated: major issue

  10. May 3, 11:43 AM

    Status updated: major issue

  11. May 3, 09:04 PM

    Report volume returned to baseline — incident resolved

Official updates

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