Cloudflare Outage History

Cloudflare experienced an issue where browser-based RDP functionality was not working with Firefox browsers, while other browsers like Chrome remained unaffected. The incident impacted Cloudflare Sites and Services and Access components for 1.7 hours. Cloudflare investigated the Firefox-specific compatibility issue during this period.

Cloudflare experienced a 35-minute outage affecting their Pages API and build system, causing customers to encounter 5xx errors and preventing builds from starting or completing successfully. The incident impacted Cloudflare Sites and Services along with the Pages platform. Cloudflare identified the issue and worked on implementing a fix to restore normal service operations.

Cloudflare Access experienced delays in propagating configuration changes to edge servers for 1.2 hours, while existing configurations and user logins remained unaffected. The issue impacted Cloudflare Sites and Services along with the Access component. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced intermittent connectivity issues at their Ashburn, VA data center (IAD) affecting North American users for 1.5 hours. The company investigated the problem and implemented a fix to restore service. The incident was resolved with continued monitoring to ensure stability.

Cloudflare experienced an issue with their 1.1.1.1 public DNS resolver that impacted users in North America for 22 minutes. The incident affected Cloudflare Sites and Services along with their Recursive DNS functionality. The issue was investigated and resolved, though specific resolution details were not provided in the incident report.

Cloudflare experienced an issue with RealtimeKit affecting Android users running version 1.6.0 and higher, impacting Cloudflare Sites and Services. Users were advised to downgrade to version 1.5.7 as a temporary workaround while Cloudflare identified and implemented a fix. The incident lasted 2.7 hours before being resolved.

Cloudflare Radar experienced response delays for 2 hours, affecting the Radar service and associated Cloudflare Sites and Services. While the services remained fully operational throughout the incident, users experienced slower response times. The issue was resolved and services returned to normal performance, with continued monitoring to ensure complete resolution.

Cloudflare experienced elevated latency affecting Durable Objects and R2 API requests in the Western North America region for 57 minutes. Users encountered timeouts and increased response times when accessing these services. The incident also impacted Cloudflare Sites and Services during this period.

Cloudflare experienced a dashboard display issue where Account API Tokens were incorrectly shown as User API Tokens, affecting the Cloudflare Dashboard interface. The issue was purely visual and did not impact existing API token functionality or API operations. The problem was identified and resolved within 34 minutes.

Cloudflare experienced CNI (Cloud Network Interconnect) performance issues affecting connectivity through the Newark, NJ data center, with customers using Equinix Cloud Connect experiencing intermittent connectivity or complete service loss. The incident impacted Cloudflare Sites and Services along with CNI services for 6.4 hours. The issue was identified and a fix was implemented to resolve the connectivity problems.