Cloudflare Outage History

The incident began during scheduled maintenance in Marseille at 1:00 AM UTC and progressed into a broader degradation affecting multiple Cloudflare services. Users reported delays and errors across Cloudflare Load Balancing and Monitoring, CDN Cache Purge, and Pages deployments, with symptoms including slow responses, intermittent failures, and 500 errors or SSL connection problems. In the Mumbai region, an uptick in HTTP errors was observed as the issue evolved, indicating a geographic extension of impact beyond a single location. Reports covered Europe and Asia, pointing to a widespread degraded experience rather than a single component outage.

Cloudflare issued six status updates during the incident, detailing ongoing investigations and regional impact. The outage lasted roughly 23 hours and was resolved with services restored by 12:05 AM UTC.

Cloudflare conducted scheduled maintenance in the Osaka region (KIX), beginning around 19:00 UTC on 7:00 PM UTC. The status page moved to a warning at 7:05 PM UTC as the work started, with a note that updates would be provided as necessary. The maintenance was regional to Osaka and did not indicate a global outage. The incident included two official status updates during its course.

The maintenance lasted about 5 hours and 5 minutes and concluded with the status returning to up at 12:05 AM UTC. Impact was limited to services routed through the Osaka (KIX) region; there were no reported global outages.

Cloudflare reported delays in processing Gateway Network Firewall logs via the Dashboard during a scheduled maintenance window in Tegucigalpa, impacting the Gateway Logs portion of Cloudflare Sites and Services / Logs. Log delivery via Logpush remained unaffected. A small number of user reports, including activity from Krasnodar, Russia, helped indicate the timing of the issue.

The outage began at Jan 5, 2026 10:50 AM UTC and was resolved by Jan 5, 2026 2:05 PM UTC, lasting about 3 hours and 15 minutes. Cloudflare issued six official status updates during the incident, noting delays in processing logs and ongoing maintenance actions, with the Logs component fluctuating before returning to normal. The incident concluded with the service returning to full operation.

The Kuala Lumpur (KUL) region underwent scheduled maintenance on 2026-01-04, during which regional Cloudflare services were temporarily affected. The maintenance window began at 6:50 PM UTC and concluded at 9:50 PM UTC, with the status page indicating the work was in progress. Updates were provided as needed, and the region returned to normal operations after the maintenance window with the status restored to operational at 9:50 PM UTC.

The incident was localized to the Kuala Lumpur region, and the status subsequently returned to up after the maintenance period. Cloudflare communicated the ongoing maintenance on their status page and indicated that updates would be provided as necessary.

Cloudflare experienced network degradation affecting users in India. The issue was identified at 9:52 AM UTC and a status update was issued at 9:55 AM UTC indicating remediation was underway. Services were restored by 11:35 AM UTC, for an outage duration of about 1 hour 40 minutes. Cloudflare's status page communications described the identified issue and the fix being implemented to remediate impact, with restoration confirmed once the problem was resolved. The impact appeared localized to India, with no broader regional effects reported.

The Cloudflare status page reported a subset of Cloudflare Workers experiencing Exceeded Memory errors, causing intermittent site loading issues for some users. The incident began at Jan 3, 2026 1:45 AM UTC and was resolved by Jan 3, 2026 6:35 AM UTC, lasting about 4 hours and 50 minutes. User reports began around 2:04 AM UTC describing problems loading some sites. Cloudflare issued 2 status updates during the event; the first noted that the issue had been identified and a fix was being implemented, and the second confirmed that services had returned to normal.

The impact was limited to a small subset of Cloudflare Workers customers and did not indicate a broad outage.

The Cloudflare Audit Logs experienced processing delays during a brief incident, resulting in delayed delivery of audit data. This issue affected a small portion of audit log processing and did not impact analytics for DNS or Rate Limiting. The outage began at 5:35 PM UTC and was resolved by 10:30 PM UTC, lasting approximately 4 hours and 55 minutes. Cloudflare issued 2 status updates over the course of the incident and then returned to normal operation. User reports during the event included access-related issues from locations such as Castleford, England and Edmonton, Alberta, Canada.

Cloudflare Sites and Services / Tunnel experienced degraded performance with increased 5xx errors in the India region, while maintenance windows were running in Campinas (VCP) and Buenos Aires (EZE). Some users in India reported SSL handshake failures (error 525), consistent with intermittent connectivity during the regional maintenance. The incident began with Campinas maintenance around Dec 31, 2025 5:30 PM UTC and evolved into broader issues affecting India in the following days.

Cloudflare issued four status updates between Dec 31, 2025 5:30 PM UTC and Jan 2, 2026 5:05 PM UTC. The India region issue was identified and a fix was being implemented starting at Jan 2, 2026 12:43 PM UTC, while Buenos Aires maintenance was noted around Jan 2, 2026 3:30 PM UTC. Service recovered by Jan 2, 2026 5:05 PM UTC. The incident’s footprint centered on the India region, with maintenance activity in the Americas.

Cloudflare carried out scheduled maintenance in the Hong Kong region, causing a temporary degradation of service for that area. The maintenance began at 5:30 PM UTC and was completed by 11:00 PM UTC, with the status page indicating the work was in progress and that updates would be provided as necessary. The Hong Kong window was localized to HKG and did not indicate broader regional or global impact.

Cloudflare Pages experienced build failures that prevented deployments for multiple customers. The outage began at 2:10 PM UTC and was resolved by 3:55 PM UTC, lasting approximately 1 hour and 45 minutes. Build processes could not complete, affecting automated builds and site deployments managed through Cloudflare Pages. Cloudflare's status updates indicated an investigation and degraded build capability, followed by a resolution confirmation. The incident involved the Cloudflare Pages component under Cloudflare Sites and Services, representing a brief degradation of service for affected customers. The provider issued two status updates during the incident.