Cloudflare Outage History

Cloudflare experienced a 1.1-hour outage affecting Workers and Pages builds along with the Pages API, causing customers to encounter 5xx errors and build failures starting at 20:22 UTC. The issue was identified and resolved by 21:12 UTC, with builds returning to stable operation. Cloudflare continued monitoring the fix to ensure service stability.

Cloudflare experienced an issue that prevented users from viewing logs in the Durable Objects dashboard, affecting Workers Observability functionality. The problem was identified after investigation and a fix was implemented. The incident lasted 3.3 hours with minor impact to Cloudflare Sites and Services.

Cloudflare experienced an issue where Challenge Pages failed to solve properly on insecure HTTP connections, affecting the Challenge Platform and Cloudflare Sites and Services. The problem was identified and resolved with a implemented fix after 1.9 hours, with monitoring continuing to ensure stability.

Cloudflare experienced control plane issues affecting Magic Transit and Magic WAN services for 1.2 hours, preventing customers from making configuration changes to GRE/IPsec tunnels, CNI connections, and routing policies through the Dashboard or API. Existing tunnel configurations and traffic forwarding continued to operate normally throughout the incident, with active tunnels and health checks remaining functional. The issue was identified and mitigation efforts were initiated to restore full service functionality.

Cloudflare experienced service degradation affecting multiple customers and services in South America, specifically impacting datacenters in Arica and Santiago, Chile. The incident lasted 1.1 hours before a fix was implemented and monitoring began. The issue affected the broader Latin America & Caribbean region during the outage period.

Cloudflare experienced issues with API token creation that resulted in "1001: Failed common permission check against resources" errors for users attempting to create tokens with Zero Trust Write permissions who were not Super Admins. The incident affected Cloudflare Sites and Services, API, and Zero Trust components for 2.8 hours, while Super Admin users and token creation requests without Zero Trust Write permissions remained unaffected. The issue has been resolved.

Cloudflare experienced dashboard login issues and API failures that prevented customers from accessing the Cloudflare Dashboard and using related APIs, with requests failing and errors being displayed. The incident affected the Dashboard, API, and Cloudflare Sites and Services components, but did not impact CDN file serving or edge security features. The issue was identified and resolved within 9 minutes after implementing a fix.

Cloudflare experienced an authentication issue with their Peering Portal (peering.cloudflare.com) caused by an outage with their third-party authentication provider, preventing customers and peers from accessing the portal for 87.7 hours. The incident did not impact Cloudflare's core CDN services or security features at the edge. The issue remained under investigation with ongoing work toward a resolution.

Cloudflare experienced an issue where custom error pages were not rendering properly, affecting Cloudflare Sites and Services for 6.7 hours. The problem was identified as a rare condition preventing some custom error pages from being displayed. Cloudflare implemented a gradual resolution to fix the rendering issue.

Cloudflare Access experienced an issue where customers were unable to upload custom block pages. The incident affected Cloudflare Sites and Services and Access components for 47 minutes. The service disruption was classified as minor and has been resolved.