Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 2 — 1d 16h disruption

May 2, 06:16 AM → May 3, 10:19 PM · 1d 16h · high

Cloudflare experienced a service disruption beginning on May 2, 2026, which was detected through user reports. The issue was resolved on May 3, 2026, at 22:19 UTC, after approximately 1 day and 16 hours.

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

Impact

During the incident, a total of 772 user reports were received, indicating a high severity disruption. The most frequently reported issues included websites being down (656 reports), slow or unresponsive service (96 reports), and login difficulties (20 reports). No specific regions were identified as disproportionately impacted by this disruption. This widespread impact on website accessibility and performance was consistent with the reported issue types.

Top reported issues

  • Website down656
  • Slow / unresponsive96
  • Login issues20

Incident timeline

  1. May 2, 06:16 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 2, 06:43 AM

    Status updated: major issue

  3. May 2, 06:53 AM

    Status updated: major issue

  4. May 2, 06:58 AM

    Status updated: major issue

  5. May 2, 07:08 AM

    Status updated: major issue

  6. May 2, 07:13 AM

    Status updated: major issue

  7. May 2, 07:23 AM

    Status updated: major issue

  8. May 2, 07:28 AM

    Status updated: major issue

  9. May 2, 07:38 AM

    Status updated: major issue

  10. May 2, 07:43 AM

    Status updated: major issue

  11. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  12. May 3, 10:19 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 06:16 AM

    Cloudflare status page acknowledged the incident.

    View official source
  2. May 3, 10:19 PM

    Root cause: Transient performance degradation with flapping behavior.

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