Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 4 — 2h 33m disruption

May 4, 12:31 PM → May 4, 03:04 PM · 2h 33m · high

A significant disruption affecting Cloudflare services was observed starting on May 4, 2026, at 12:31 PM UTC. The issue was resolved on May 4, 2026, at 3:04 PM UTC, after approximately 2 hours and 33 minutes.

Peak reports
8
in 15 min
Total reports
68
during the incident
Duration
2h 33m
tracked by PulseWatch

Impact

During this incident, users reported widespread issues with website accessibility and performance. The most common reports indicated websites being down entirely, followed by reports of slow or unresponsive services. A smaller number of users also experienced API-related problems. The disruption was detected through user reports and monitored by PulseWatch, with the issue being correlated across multiple signal groups.

Top reported issues

  • Website down44
  • Slow / unresponsive20
  • API issues4

Incident timeline

  1. May 4, 12:31 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 12:45 PM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 4, 02:08 PM

    Status updated: major issue

  4. May 4, 03:04 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 12:31 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