Cloudflare Outage History

Cloudflare conducted scheduled maintenance in the Johannesburg region (JNB), beginning late 10:30 PM UTC. The status page showed the region as in progress and later listed as degraded (warn) during the maintenance window. This was a regional operation affecting traffic routed through the Johannesburg edge and causing degraded performance for workloads in that area. There were no observed global impacts, and user reports were not noted during this window.

Maintenance completed with the Johannesburg region returning to normal by 1:05 PM UTC, after roughly 14 hours and 35 minutes. The provider issued two official status updates during the window documenting the in-progress maintenance and the eventual restore. The affected component was the Johannesburg edge region (JNB).

Cloudflare performed scheduled maintenance in the Tokyo (NRT) region on 2026-02-05. The incident began at 5:00 PM UTC and a degraded service state persisted through the maintenance window, with updates indicating work was in progress. The Tokyo region experienced intermittent connectivity and reduced performance during this period. A small number of user reports were logged during the window, including a report from Europe, suggesting some visibility beyond Tokyo.

The Cloudflare Stream service experienced an outage affecting live broadcasts, beginning at 4:50 PM UTC and lasting about 50 minutes until 5:40 PM UTC. During this window, users could not load live streams via the Stream player, while on‑demand videos remained accessible. The incident coincided with broader degraded performance across Cloudflare services, including increased latency at the Newark, NJ data center and a rise in 404/500 errors for Cloudflare Pages. Additional issues were observed with DNS Updates, Digital Experience Monitoring (DEX) latency, and Browser Rendering, with regional maintenance notices appearing in multiple locations.

Cloudflare conducted scheduled maintenance in the Bangkok region beginning on 5:02 PM UTC. The Cloudflare status page indicated the work was in progress and could have caused degraded performance or intermittent connectivity for traffic in the Bangkok area.

The maintenance lasted about 20 hours and was completed with the status returning to up on 1:05 PM UTC.

Cloudflare experienced a broad degradation across multiple services, including D1 databases, Durable Objects, and R2 storage, causing latency, timeouts, and errors for many users globally. The incident began at 9:10 PM UTC and persisted until 1:05 PM UTC, lasting about 7 days and 16 hours. Reports from North America, Europe, and Asia Pacific indicated degraded performance and intermittent access across various regions, with services such as D1, Durable Objects, R2, Workers KV, Pages, Workers, and Access impacted. The outage spanned a broad set of Cloudflare components, and remediation efforts were rolled out over the course of the incident.

Cloudflare issued numerous status updates detailing elevated errors, timeouts, and progressive fixes across networks and regions. The updates described ongoing remediation, code changes, and staged recoveries, with some components returning to normal in phases while others required additional work. By 1:05 PM UTC many affected services had stabilized, though continued monitoring and validation were noted in communications.

During scheduled maintenance, Cloudflare entered a degraded state at Jan 23, 2026 3:05 PM UTC as Durable Objects across multiple regions began reporting elevated errors. This affected SQLite-backed Durable Objects and the D1 service, causing intermittent failures for apps relying on these components. The issue appeared system-wide across several regions, tied to the ongoing maintenance.

Cloudflare scheduled maintenance in the San José region began at 4:00 AM UTC and caused temporary degradation for some users. The maintenance window lasted about 10 hours and 5 minutes and concluded by 2:05 PM UTC.

Cloudflare issued 2 status updates during the incident to communicate progress. A London-based user reported website errors during the window, suggesting limited regional impact while the maintenance was ongoing.

Cloudflare experienced a multi-hour incident beginning during scheduled maintenance on Jan 22, 2026 4:00 PM UTC, which led to degraded performance across Cloudflare Sites and Services. The issue affected two components, Notifications and Network, with users seeing 404 errors on L3/4 DDoS alert links in the dashboard and, in some cases, origin-related errors such as Error 523. A user reported issues around 9:30 PM UTC. The incident overlapped with Chennai maintenance and other regional activities as updates rolled out over the evening. The outage lasted about 10 hours and 5 minutes and was resolved by Jan 23, 2026 2:05 AM UTC.

Cloudflare conducted scheduled maintenance in the Bangkok region beginning at 5:00 PM UTC and lasting until 2:00 PM UTC. During this period, Cloudflare listed a degraded state on its status page as the maintenance proceeded, indicating ongoing work in Bangkok and resulting in partial disruption for some users. The window spanned about 21 hours.

Cloudflare issued two official updates during the incident, and user reports during the window included activity from Yorkville, Illinois, demonstrating that traffic journeys through affected infrastructure. The service returned to normal after 2:00 PM UTC as the maintenance concluded.

Cloudflare began experiencing a minor increase in errors on D1 and Durable Objects, potentially impacting some customers. The issue also coincided with Dashboard SSO login problems, affecting sign-in for multiple accounts. The outage started at Jan 20, 2026 2:25 PM UTC and a fix was implemented by 3:51 PM UTC, after which Cloudflare continued to monitor results as investigations proceeded. Affected components included Durable Objects, D1, and the Dashboard.

Over the course of the incident, Cloudflare issued 9 status updates. Digital Experience Monitoring (DEX) underwent scheduled maintenance from Jan 21, 2026 12:00 PM UTC to Jan 21, 2026 4:05 PM UTC while the platform was restored, with the incident resolving by Jan 21, 2026 4:05 PM UTC. The events highlighted multi-component impact across Durable Objects, D1, Dashboard, and DEX, and required ongoing remediation before full service restoration.