Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 3 4h 48m disruption

May 3, 03:45 PM → May 3, 08:34 PM · 4h 48m · high

On May 3, 2026, a service disruption affecting Cloudflare was detected through user reports. The incident began at approximately 15:45 UTC and was fully resolved by 20:34 UTC, resulting in a total disruption of 4 hours and 48 minutes.

Peak reports
12
in 15 min
Total reports
116
during the incident
Duration
4h 48m
tracked by PulseWatch

Impact

The outage was categorized as high severity, with a total of 116 user reports received during the incident. The most frequently reported issues included websites being down, login difficulties, and slow or unresponsive service. At its peak, 12 reports were received within a 15-minute period. No specific regional impact was recorded during this event.

Top reported issues

  • Website down80
  • Login issues20
  • Slow / unresponsive16

Incident timeline

  1. May 3, 03:45 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 04:00 PM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  3. May 3, 04:14 PM

    Status updated: major issue

  4. May 3, 04:28 PM

    Status updated: major issue

  5. May 3, 04:38 PM

    Status updated: major issue

  6. May 3, 04:43 PM

    Status updated: major issue

  7. May 3, 04:53 PM

    Status updated: major issue

  8. May 3, 04:58 PM

    Status updated: major issue

  9. May 3, 08:34 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 03:45 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