SJC (San Jose) on 2026-08-17
Started · 2026-08-14 13:51 UTC
Official incident updateLive outage monitoring
Real-time status for the websites and services you rely on.
Cloudflare status · cloudflare.com
CDN, DNS, and security platform.
Possibly — Cloudflare may have issues
cloudflare.com may be experiencing issues such as errors or slow responses. The latest automated check was run 2026-08-17 10:37 UTC from primary location. This is not a confirmed global outage.
423 of 467 operational · 44 with issues
Started · 2026-08-14 13:51 UTC
Official incident updateStarted · 2026-08-14 07:00 UTC
Official incident updateStarted · 2026-08-12 23:50 UTC
Official incident updateCrowd reports submitted on this site for Cloudflare over the last 24 hours.
0 reports
Loading user-report chart…
Not enough independent response-time samples yet to draw this chart.
Availability from independent checks, with recorded incidents and downtime in each window. Monitoring since Aug 14, 2026. Period percentages appear only after we have full coverage for that window.
Today
—
Not enough history
Last 7 days
—
Not enough history
Last 30 days
—
Not enough history
Last 365 days
—
Not enough history
Recorded outages with duration and start time.
Last recorded 2026-08-17 07:47 UTC
| Incident | Duration | Started |
|---|---|---|
Increased Errors for Durable Objects Resolved | 1h 23m | 2026-08-17 07:47 UTC |
Durable Objects and Cloudflare Workflows availability drop Resolved | 41 min | 2026-08-14 19:27 UTC |
Increased network congestion in the Eastern US Resolved | 55 min | 2026-08-14 15:34 UTC |
SJC (San Jose) on 2026-08-17 Scheduled | Ongoing | 2026-08-14 13:51 UTC |
ORD (Chicago) on 2026-08-17 Scheduled | Ongoing | 2026-08-14 07:00 UTC |
TXL (Berlin) on 2026-08-17 Resolved | 3d 18h | 2026-08-13 09:20 UTC |
YUL (Montréal) on 2026-08-17 Scheduled | Ongoing | 2026-08-12 23:50 UTC |
KUL (Kuala Lumpur) on 2026-08-14 Resolved | 3d 4h | 2026-08-11 17:20 UTC |
Who's Down Today monitors Cloudflare independently of the company that runs it. We send reachability checks from our primary location every minute and record response time, HTTP errors, and timeouts.
When Cloudflare publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.
This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.
Possibly — Cloudflare may have issues
cloudflare.com may be experiencing issues such as errors or slow responses. The latest automated check was run 2026-10-01 22:55 UTC from primary location. This is not a confirmed global outage.
cloudflare.com may have issues such as errors or slow responses.
This is not a confirmed global outage. Report what you see below.