Live  /  Cloudflare  /  Incident

Cloudflare: Increased errors for R2 and Tiered Cache

Cloudflare · cloudflare.comMinor incidentResolved2026-11-14 06:45 UTC
Public — what happened

Summary

Cloudflare said some customers using its R2 storage service and its Tiered Cache feature received errors, with a small share of requests failing. The company reported that a network connectivity problem between several of its data centers began at 05:00 UTC on 2026-11-14, and that people in Chicago and Newark were hit hardest while other locations saw fewer problems. Cloudflare said error rates had fallen close to normal by 05:30 UTC while it monitored the underlying network issue, and it marked the incident resolved at 06:45 UTC.

Affected

Chicago, United States - (ORD), R2, Newark, United States - (EWR)

As listed on Cloudflare’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

What SquidGrid measured

SquidGrid measured 189 internet paths into Cloudflare’s network during this incident. None of them ran meaningfully slower than the same paths the day before.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Cloudflare against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Cloudflare: paths off baseline right now, where on the route conditions change, and its full incident track record.

Included with any paid plan.

Open the Cloudflare report →

More from Cloudflare

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Cloudflare status & history page.

Related: Cloudflare status & history. SquidGrid is not affiliated with Cloudflare.