Cloudflare incident history

Right now: minor open (2 open), by Cloudflare's own status page, mirrored every five minutes.

50
incidents kept since 9 Sept 2026
50
in the last 30 days
1h 14m
median time to resolve, once posted
42%
resolved within an hour

How far back this goes: Cloudflare's feed exposed its 50 most recent incidents when we began mirroring on 25 September 2026, so this page covers 16 days so far and grows from here. Impact labels (0 major or critical) are Cloudflare's own. We don't compare providers on this page; the windows aren't equal yet.

What our probes saw

No monitor that declares Cloudflare as a dependency was evaluated during these incidents, so there's nothing to add from our side yet. This fills in as more sites behind Cloudflare are watched.

Which parts of Cloudflare the incidents touched

Network
4
Durable Objects
3
Replicate
3
R2
2
Rules
2
Containers
2

Every incident we hold, newest first

25 Sept 2026
minor
—
25 Sept 2026
minor
1h 32m
25 Sept 2026
minor
14h 45m
24 Sept 2026
minor
3h 4m
23 Sept 2026
minor
43m 38s
21 Sept 2026
none
—
21 Sept 2026
minor
11m 18s
17 Sept 2026
minor
20h 42m
16 Sept 2026
minor
17m 15s
15 Sept 2026
minor
19m 48s
14 Sept 2026
minor
1d 2h
9 Sept 2026
minor
2d 8h

Source: Cloudflare's public status page at www.cloudflarestatus.com, mirrored every five minutes. Data as JSON: /upstream/cloudflare/incidents.json. CC BY 4.0.

If your site depends on Cloudflare, Repose holds the page when the cause is upstream. How the hold decision works →