Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 2 — 1d 18h disruption

May 2, 04:00 AM → May 3, 10:34 PM · 1d 18h · high

Cloudflare experienced a service disruption beginning on May 2, 2026. This incident was detected through user reports indicating widespread issues. The disruption was resolved on May 3, 2026, at 22:34 UTC.

Peak reports
10
in 15 min
Total reports
828
during the incident
Duration
1d 18h
tracked by PulseWatch

Impact

During the incident, users reported a range of issues, with a total of 828 reports received. The most frequently reported problem was websites being down, accounting for 700 reports. Additionally, 108 users experienced slow or unresponsive services, and 20 users reported login difficulties. No specific top impacted regions were recorded, suggesting a broad impact across the user base.

Top reported issues

  • Website down700
  • Slow / unresponsive108
  • Login issues20

Incident timeline

  1. May 2, 04:00 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 2, 04:23 AM

    Status updated: possible issue

  3. May 2, 04:28 AM

    Status updated: major issue

  4. May 2, 04:43 AM

    Status updated: major issue

  5. May 2, 04:53 AM

    Status updated: major issue

  6. May 2, 04:58 AM

    Status updated: major issue

  7. May 2, 06:38 AM

    Status updated: major issue

  8. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  9. May 3, 10:34 PM

    Report volume returned to baseline — incident resolved

Official updates

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