Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 3 — 3h 4m disruption

May 3, 05:15 PM → May 3, 08:19 PM · 3h 4m · high

On May 3, 2026, Cloudflare experienced a service disruption. This incident was detected by user reports and began at approximately 17:15 UTC. The issue was resolved by 20:19 UTC on the same day.

Peak reports
10
in 15 min
Total reports
72
during the incident
Duration
3h 4m
tracked by PulseWatch

Impact

The service disruption primarily impacted users reporting issues with websites being down and login difficulties. A total of 72 user reports were received during the incident, with 'Website down' being the most frequently reported issue type (52 reports), followed by 'Login issues' (20 reports). No specific regional impact was recorded during this period. This incident was initially identified through these user reports.

Top reported issues

  • Website down52
  • Login issues20

Incident timeline

  1. May 3, 05:15 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 05:23 PM

    Status updated: major issue

  3. May 3, 05:28 PM

    Status updated: major issue

  4. May 3, 05:30 PM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  5. May 3, 05:38 PM

    Status updated: major issue

  6. May 3, 05:43 PM

    Status updated: major issue

  7. May 3, 05:53 PM

    Status updated: major issue

  8. May 3, 05:58 PM

    Status updated: major issue

  9. May 3, 06:08 PM

    Status updated: major issue

  10. May 3, 06:13 PM

    Status updated: major issue

  11. May 3, 06:23 PM

    Status updated: major issue

  12. May 3, 06:28 PM

    Status updated: major issue

  13. May 3, 08:19 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 05:15 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