Cloudflare Outage History

Cloudflare recorded a brief regional degradation affecting access to Cloudflare R2 from the APAC region, with elevated error rates impacting Images, R2, Stream, and Cache Reserve. The incident began at 11:25 PM UTC and was resolved by 11:30 PM UTC, spanning about 5 minutes. The provider issued 2 official updates during the outage, outlining a mitigation and subsequent return to normal. Users in APAC may have experienced intermittent access or slower responses during the window, with no broader global impact indicated.

An outage at Cloudflare affected multiple core services including the Cloudflare Dashboard, Cloudflare API, Workers, and network performance. Users reported widespread errors and degraded performance, with many sites experiencing 500 responses and timeouts. The disruption began at 9:00 AM UTC and persisted for about four hours, with full recovery by 1:05 PM UTC.

Cloudflare published several updates detailing issues across Dashboard/API, Bot Management, and network performance in various regions. Updates were issued at multiple timestamps during the incident (for example 9:00 AM UTC, 9:25 AM UTC, 9:35 AM UTC, 10:15 AM UTC, and 1:05 PM UTC). A surge in user reports across regions underscored the broad reach of the disruption, which gradually subsided as affected components came back online.

Cloudflare ran a scheduled maintenance window in the Calgary (YYC) region on 2025-12-02. The maintenance began at Dec 2, 2025 4:05 PM UTC and lasted about 7 hours and 35 minutes, ending at Dec 2, 2025 11:35 PM UTC. Updates on the status page described the work as in progress and noted the regional focus in Calgary. The window impacted services in the YYC region during the maintenance period.

Cloudflare experienced a brief degradation in SSL certificate provisioning for Custom Hostnames, causing delays in provisioning and renewing new certificates. Existing SSL certificates in production remained unaffected and continued to operate normally. The outage began at 2:45 PM UTC and was resolved by 3:50 PM UTC.

Cloudflare posted status updates during the incident, noting an investigation and later restoration of provisioning. The incident was short lived, with the service returning to normal after a little over an hour. The provider issued 2 status updates over the course of the incident.

Cloudflare conducted scheduled maintenance in the San José (SJO) region, causing a brief period of degraded performance for users in and around the area. The maintenance window began around 9:01 AM UTC and the service was returned to normal by 1:05 PM UTC.

During the window, some users reported intermittent connectivity, including a sample from Bandung, Indonesia at 11:08 AM UTC.

Cloudflare carried out scheduled maintenance in the Amsterdam (AMS) region beginning at 12:00 AM UTC. The AMS region was listed as undergoing maintenance, and users could experience intermittent connectivity during the window. The status page note stated In progress - Scheduled maintenance is currently in progress. The maintenance window ran from 12:00 AM UTC to 6:05 AM UTC, about 6 hours and 5 minutes.

At 6:05 AM UTC, Cloudflare flagged the maintenance as completed and services in the AMS region returned to normal. The incident involved two official status updates during its course and appeared to affect only the Amsterdam region rather than the wider Global network.

Cloudflare reported longer-than-usual processing times and delivery delays for messages passing through Email Security Area1 and Email Security Zero Trust. The impact was limited to email processing, resulting in slower handling and delivery of messages during the incident.

The issue began at 8:05 PM UTC and was resolved by 10:55 PM UTC, lasting roughly 2 hours and 50 minutes. Cloudflare issued two status updates during the incident, noting the degraded processing and later restoration of Email Security services for the affected components.

After the updates, email processing returned to normal as services stabilized.

Cloudflare experienced delays impacting Cloudflare Logs (Logpush) processing and Workers Analytics in the EU, causing slower log delivery and analytics visibility for some users. The outage began at 7:00 AM UTC and was resolved by 1:00 PM UTC, for a total duration of about 6 hours. The incident affected two components and prompted a noticeable spike in user-reported issues during the window.

Cloudflare reported a brief network performance issue affecting the North America / Newark, NJ (EWR) region. Users routing through Newark may have experienced slower connections for about 30 minutes. The incident began at 12:30 AM UTC with an investigation notice and was resolved by 1:00 AM UTC as services returned to normal. Cloudflare issued two status updates during the incident to communicate the investigation and restoration.

Cloudflare reported an incident affecting Custom Error Pages, with some visitors failing a challenge and seeing the standard Cloudflare 500 error page instead of the customized content. The outage began at Nov 29, 2025 4:00 PM UTC and lasted for about 3 hours and 5 minutes, with services returning to normal by Nov 29, 2025 7:05 PM UTC. This caused degraded error handling across sites relying on Cloudflare's custom error pages. The provider issued two status updates during the incident as they investigated and then resolved the issue.