Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 3 8h 48m disruption

May 3, 12:01 PM → May 3, 08:49 PM · 8h 48m · high

A service disruption affecting Cloudflare was detected on May 3, 2026. This incident, initially identified through user reports, began at approximately 12:01 UTC and was resolved by 20:49 UTC on the same day.

Peak reports
13
in 15 min
Total reports
196
during the incident
Duration
8h 48m
tracked by PulseWatch

Impact

During the 8-hour and 48-minute incident, a total of 196 user reports were received, with a peak of 13 reports within a 15-minute period. The most frequently reported issues included websites being down (144 reports), slow or unresponsive service (32 reports), and login difficulties (20 reports). No specific regional impact was identified from the user reports.

Top reported issues

  • Website down144
  • Slow / unresponsive32
  • Login issues20

Incident timeline

  1. May 3, 12:01 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 12:15 PM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  3. May 3, 12:23 PM

    Status updated: major issue

  4. May 3, 12:28 PM

    Status updated: major issue

  5. May 3, 12:38 PM

    Status updated: major issue

  6. May 3, 12:43 PM

    Status updated: major issue

  7. May 3, 12:53 PM

    Status updated: major issue

  8. May 3, 12:58 PM

    Status updated: major issue

  9. May 3, 01:08 PM

    Status updated: major issue

  10. May 3, 01:13 PM

    Status updated: major issue

  11. May 3, 04:09 PM

    Status updated: major issue

  12. May 3, 08:49 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 12:01 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