Cloudflare Outage History

Cloudflare conducted scheduled maintenance in the ORD (Chicago) region beginning at 8:00 AM UTC. The status page listed the work as in progress during the window and noted that updates would be provided as necessary. The maintenance concluded with services restored by 12:20 PM UTC, after approximately 4 hours and 20 minutes. The provider issued two status updates during the incident.

Cloudflare experienced a brief degraded state as configuration changes failed to propagate promptly to Edge data centers due to an orchestration service issue in a core datacenter. This caused delays in applying updates and feature changes across Cloudflare's edge network. The incident began at 9:50 PM UTC and was resolved by 11:10 PM UTC, lasting about 1 hour 20 minutes. Cloudflare issued 2 status updates during the incident to communicate investigation and resolution steps. Propagation returned to normal once the orchestration issue was addressed.

Cloudflare carried out scheduled maintenance in the Durban region on 1:00 AM UTC. During the work, the status page listed the incident as in progress with a note that scheduled maintenance was ongoing. This region-specific activity could have impacted traffic routed through Durban-based Cloudflare infrastructure during the window. The maintenance window lasted just over 3 hours and concluded with the status returning to up by 4:05 AM UTC. The Cloudflare status page issued two updates during the event: one to indicate maintenance was in progress and another to confirm completion.

The Cloudflare 1.1.1.1 public DNS resolver experienced an outage affecting DNS resolution for many users. The issue began on 10:15 PM UTC as the status page switched from up to warn with a note that the issue could impact multiple users. User reports from around the world described DNS failures and inability to resolve domain names, including services like security.cloudflare-dns.com. The outage lasted about 1 hour and 5 minutes and was resolved by 11:20 PM UTC.

Cloudflare conducted scheduled maintenance in the Tampa area (TPA) on 2:00 PM UTC. The status page indicated maintenance in progress at 2:05 PM UTC and noted that the work was in progress. The regional scope limited the impact to the Tampa area, affecting services routed through Cloudflare in that locale. The maintenance was completed and services returned to normal by 7:05 PM UTC. During the incident, Cloudflare issued two status updates to communicate the in-progress maintenance and the subsequent completion.

Cloudflare reported a problem with its Verified Bots feature that led to an elevated rate of traffic being flagged as automated for certain Google bots. This partial outage did not affect all Cloudflare services, but could impact how automated requests were classified during the incident. The status page indicated the issue was under investigation with mitigation efforts underway, and there were subsequent updates as the situation evolved.

Cloudflare reported a brief issue with cron triggers not executing for some customers, impacting scheduled tasks in Cloudflare Workers. The problem began at Jul 12, 2025 12:15 AM UTC and was resolved by Jul 12, 2025 12:35 AM UTC, lasting about 20 minutes. The affected component was Cloudflare Sites and Services / Workers.

Cloudflare logged updates on its status page during the incident and restored normal operation after mitigation. The incident included two official status updates detailing the investigation and resolution.

Cloudflare carried out scheduled maintenance at the Frankfurt FRA region, resulting in a temporary regional disruption during the work window. The maintenance began at 12:00 AM UTC and concluded by 4:05 AM UTC. Cloudflare posted two updates on its status page during the incident to inform users of the maintenance progress and completion.

Cloudflare experienced an elevated level of HTTP errors affecting websites and services that rely on its network, resulting in degraded performance for some users. The incident began at Jul 10, 2025 10:55 PM UTC and lasted about 40 minutes, with service returning to normal by Jul 10, 2025 11:35 PM UTC.

Cloudflare issued an official status update indicating they were investigating the increased errors and working to mitigate the problem, and the service returned to the up state after remediation.

Cloudflare experienced brief connection failures affecting a subset of zones, causing intermittent access issues for websites relying on Cloudflare's network. The incident began at Jul 10, 2025 9:39 PM UTC and was resolved by Jul 10, 2025 10:00 PM UTC after a fix was applied and monitoring confirmed stability. Cloudflare issued two status updates during the incident, noting the issue and subsequent recovery. The impact was limited to certain zones and did not represent a global outage.