Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 2 — 1d 22h disruption

May 2, 12:10 AM → May 3, 10:49 PM · 1d 22h · high

On May 2, 2026, Cloudflare experienced a service disruption that was first detected through user reports. The incident led to various service issues for users. Services were fully restored by May 3, 2026.

Peak reports
11
in 15 min
Total reports
948
during the incident
Duration
1d 22h
tracked by PulseWatch

Impact

Users reported a range of issues during the disruption, with a total of 948 reports received. The most frequently reported problems included websites being down, slow or unresponsive services, and API issues. A smaller number of users also reported login difficulties. While no specific regional impact was identified, these issues were observed across the user base.

Top reported issues

  • Website down764
  • Slow / unresponsive132
  • API issues32
  • Login issues20

Incident timeline

  1. May 2, 12:10 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  3. May 3, 10:49 PM

    Report volume returned to baseline — incident resolved

Official updates

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