Skip to content
Back to CloudflareIncident Postmortem
Cloudflare logo

Cloudflare

Tracked by PulseWatch

Auto-drafted postmortem

Cloudflare outage on May 5 — 48 minute disruption

May 5, 11:45 AM → May 5, 12:34 PM · 48 minutes · high

A high-severity incident impacted Cloudflare services on May 5, 2026. The issue began at 11:45 UTC and was resolved at 12:34 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 experiencing website downtime and slow or unresponsive service. The majority of reports indicated that websites were down, with a significant number also noting unresponsiveness. The issue was observed across multiple user reports, and while no specific regions were identified as top impacted areas, the overall user experience was degraded. The incident was correlated across multiple monitoring signals.

Top reported issues

  • Website down16
  • Slow / unresponsive8

Incident timeline

  1. May 5, 11:45 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 5, 12:00 PM

    Peak of 8 reports in 15 minutes (baseline 1.5)

  3. May 5, 12:13 PM

    Status updated: major issue

  4. May 5, 12:34 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 5, 11:45 AM

    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