Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 4 — 48 minutes disruption

May 4, 06:30 PM → May 4, 07:19 PM · 48 minutes · high

A high-severity incident impacted Cloudflare services on May 4, 2026. The issue began at 18:30:47 UTC and was resolved at 19:19:20 UTC, resulting in a total disruption of 48 minutes. This incident was detected via user reports.

Peak reports
10
in 15 min
Total reports
24
during the incident
Duration
48 minutes
tracked by PulseWatch

Impact

During this incident, users reported that their websites were down or experiencing slow and unresponsive behavior. The issue was detected by PulseWatch through user reports, with a peak of 10 reports in a 15-minute window and a total of 24 reports during the event. No specific regions were identified as being more impacted than others.

Top reported issues

  • Website down16
  • Slow / unresponsive8

Incident timeline

  1. May 4, 06:30 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 06:45 PM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  3. May 4, 06:53 PM

    Status updated: major issue

  4. May 4, 06:58 PM

    Status updated: major issue

  5. May 4, 07:19 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 06:30 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-lite