Cloudflare had two separate incidents on 5 October: a long-running API Shield JWT validation fault lasting 11h 45m, and a shorter Durable Objects availability issue in Eastern North America lasting 5h 22m. Both were Cloudflare-side faults, confirmed on Cloudflare's own status page.
Started
10:55 UTC
Duration
Lasted 11h 45m
Source
IsDown
Next time
Cloudflare is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Cloudflare Sites and Services, Containers, Durable Objects, R2, Workflows, API Shield
What happened?
Cloudflare logged six affected components across the day: Cloudflare Sites and Services, API Shield, Containers, Durable Objects, R2 and Workflows. The first incident started at 10:55 UTC and hit API Shield's JWT validation for customers using symmetric keying material. Cloudflare said it was investigating at 10:55, identified the issue at 11:24 and said a fix was implemented and being monitored at 20:09, which puts the total at 11h 45m. The second incident started later, at 17:14 UTC, and affected Durable Objects and dependent services specifically in Eastern North America. Cloudflare's wording there described "decreased availability" rather than a full outage, and a fix was reported implemented by 17:53, closing out at 5h 22m. Five updates in total were published across both incidents, and no further detail beyond "fix implemented, monitoring results" was given for either. No user reports were filed during the window on this page's record. Cloudflare's own status history shows 190 incidents in the last 90 days with a median duration of 1 hour 48 minutes, so an 11h 45m incident sits well above the usual pattern for them. The record does not say why the API Shield validation broke or why Durable Objects availability dropped specifically in that one region, so the underlying cause for either incident is not on the record.
Learning
Our probes, covering api-control, dns-1111 and edge-data across EU and NA regions, stayed at 100% uptime across 24h, 7d and 30d windows, and this incident was not registered against them. That is not a contradiction. API Shield JWT validation and Durable Objects availability in one region are both narrow, feature-level faults that sit behind Cloudflare's edge, not faults in the edge network's basic reachability, which is what uptime checks against DNS and edge endpoints are built to catch. A symmetric-key JWT validation path or a regional Durable Objects namespace can fail entirely while the rest of Cloudflare answers every request normally, so a green external check and a real customer-facing fault can both be accurate at the same time. If your product depends on API Shield or Durable Objects specifically, a general reachability check on your own endpoints would not have told you anything was wrong, because the failure sat inside Cloudflare's service logic, not in the path your monitoring walks. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
