Cloudflare Outage History

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.

Cloudflare experienced network performance issues in Frankfurt, Germany, causing some users to encounter increased latency or timeouts for 23 minutes. The issue was identified and a fix was implemented, with monitoring continuing to ensure resolution.

Cloudflare One Client users in the Texas region experienced performance degradation and increased latency for 49 minutes. The incident affected Cloudflare Sites and Services along with Zero Trust components. Cloudflare actively troubleshot and resolved the connectivity issues with their Texas datacenter region.

Cloudflare experienced a 14-minute incident where users were unable to access the settings page for Cloudflare Pages Projects, particularly affecting projects without connected repositories. The issue impacted Cloudflare Sites and Services and Pages components. Cloudflare investigated and resolved the access problem.

Cloudflare experienced elevated errors and latency for R2 storage services in the Western North American region, affecting customers using R2 and Cloudflare Sites and Services. The incident lasted 1.3 hours, during which users experienced increased response times and higher error rates when accessing R2 storage. A fix was implemented and the service was restored to normal operation.

Cloudflare experienced issues with their Images service when transforming images from R2 buckets, causing errors for customers serving image transformations on free zones. The incident affected Cloudflare Sites and Services and the Images component for 31 minutes. A fix was implemented and the service was restored to normal operation.