Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 2 1d 12h disruption

May 2, 09:30 AM → May 3, 09:49 PM · 1d 12h · high

Cloudflare experienced a service disruption beginning on May 2, 2026, which was initially detected through user reports. This high-severity incident impacted various users globally. The disruption was fully resolved on May 3, 2026.

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

Impact

During the incident, users reported a range of issues, with a total of 684 reports received. The most frequently reported problem was 'Website down,' accounting for 592 reports. Additionally, users experienced 'Slow / unresponsive' services (72 reports) and 'Login issues' (20 reports). These reports indicate a broad impact on user access and functionality across the Cloudflare platform.

Top reported issues

  • Website down592
  • Slow / unresponsive72
  • Login issues20

Incident timeline

  1. May 2, 09:30 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 2, 09:53 AM

    Status updated: major issue

  3. May 2, 09:58 AM

    Status updated: major issue

  4. May 2, 10:08 AM

    Status updated: major issue

  5. May 2, 10:13 AM

    Status updated: major issue

  6. May 2, 10:23 AM

    Status updated: major issue

  7. May 2, 10:28 AM

    Status updated: major issue

  8. May 2, 10:38 AM

    Status updated: major issue

  9. May 2, 10:43 AM

    Status updated: major issue

  10. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  11. May 3, 09:49 PM

    Report volume returned to baseline — incident resolved

Official updates

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