Cache purge delays in Qingdao Shandong, China
Last updateresolvedOct 31 · 06:57 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗

checked Nov 1, 2026 7:34 AM UTC · Cloudflare's official status page
Cloudflare is up and running.
All components operational
Statusfield watches Cloudflare alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
99 reports published by Cloudflare in the last 30 days · 1 still open
When Cloudflare breaks, it is typically resolved in 1h 39m — median across 21 resolved incidents over 30 days.
resolvedOct 31 · 06:57 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 30 · 03:48 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 29 · 21:50 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 29 · 16:50 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 29 · 16:33 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 29 · 12:10 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 29 · 11:47 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
investigatingOct 29 · 09:24 UTC
Cloudflare is investigating an issue where success rates and SLIs for Workflows operations have been dipping since approximately 07:00 UTC. Customers may experience increased errors or failures when running workflows. Our team is actively investigating the root cause to restore normal service.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 29 · 11:49 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 29 · 08:28 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 29 · 00:35 UTC
Between October 28 23:25 - October 29 00:35 UTC, Cloudflare experienced issues with network performance in Queretaro, Mexico. This resulted in elevated 5xx errors, latency and connection timeouts for traffic passing through this location. This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 28 · 21:12 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 28 · 11:10 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 28 · 22:18 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 28 · 03:28 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 22:58 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 21:58 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 17:09 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 17:02 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 16:14 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 15:12 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 12:55 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 08:17 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 27 · 01:15 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 26 · 16:03 UTC
Queue times have returned to normal
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 26 · 09:03 UTC
Between 08:21 and 09:03 UTC, Cloudflare observed localized network degradation affecting traffic routed through the Chicago (ORD) data center. Customers may have experienced intermittent latency and connection timeouts during this period.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 24 · 13:57 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 24 · 03:09 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 23 · 18:43 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 23 · 20:37 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 23 · 09:22 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 23 · 09:42 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 23 · 00:09 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 23 · 00:10 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 22 · 17:31 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 22 · 22:00 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 22 · 16:15 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 22 · 02:09 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 22 · 00:35 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 21 · 21:21 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 21 · 19:57 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 20 · 20:16 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 20 · 06:32 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 20 · 22:46 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 19 · 11:50 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 18 · 08:50 UTC
Due to unexpected prefix withdrawals on peering links in IAD and CMH (Ashburn, Virginia and Columbus, Ohio, in the United States) on an external provider, customers experienced increased latency and timeouts from 08:00 to 08:50 UTC. Services have fully normalized following the restoration of prefix advertisements.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 16 · 19:09 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 16 · 13:03 UTC
Between 12:58 and 13:03 UTC, Cloudflare experienced an elevated rate of HTTP 5xx errors in Ashburn (IAD).
The incident is now resolved, and systems are fully operational.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 16 · 11:24 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 16 · 09:59 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 16 · 07:30 UTC
Cloudflare investigated and resolved issues with network performance in Bangkok, Thailand. There may have been elevated response times and an increase in 5xx errors between 06:48 and 07:30 UTC. This has been resolved and normal operations have resumed.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 16 · 02:11 UTC
Between 01:13 AM and 02:11 AM UTC, network performance at our ICN-A colo in Seoul was impacted. Users downstream of KINX may have experienced increased latency (TTFB) and elevated Network Error Logging (NEL) metrics due to network path congestion. Performance metrics have since returned to normal baselines, and the issue is now fully resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 16 · 01:06 UTC
Workers Cron Triggers have stabilized
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 21:38 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 17:46 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 21:26 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 16:10 UTC
Cloudflare resolved an incident where we observed network performance issues in our Kuala Lumpur (KUL) facility. Customers may have observed elevated error rates and/or increased latency today, 2026-10-15, between approximately 16:10 and 16:15 UTC.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 18:00 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 18:19 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 20:39 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 10:02 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 09:37 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 06:46 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 14 · 07:51 UTC
Cloudflare is aware of, and has resolved, an increased level of HTTP errors in London (LHR), between 07:43 UTC and 07:51 UTC. Services have resumed normal operation after this time.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 01:29 UTC
Workers Cron Trigger backlogs have cleared and appear healthy. Cron Trigger schedules should be executing as expected. Some schedule redeploys may be required for a small fraction of Workers who were impacted during the incident.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 14 · 05:20 UTC
Customers reaching Los Angeles (LAX) colo may have seen an elevate number of errors during the time. The problem has been mitigated, and we are currently monitoring.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 14 · 06:45 UTC
Mitigations have been put in place to prevent recurrence.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 14 · 04:12 UTC
For about 30 minutes there was reduced availability for customers using the OBS API. This has been identified, and we are back to normal for now.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 14 · 03:30 UTC
Cloudflare observed possible network congestion in Dallas, TX, United States (DFW) between 14th October 03:02–03:30 UTC. The issue has fully resolved, and we are monitoring for stability.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 13 · 22:44 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 13 · 17:07 UTC
Cloudflare saw issues with network performance in IAD that resulted in an increase in errors across Cloudflare services. Users may have experienced increases errors or timeouts reaching Cloudflare’s network or services.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 14 · 00:09 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 16 · 00:36 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 13 · 14:56 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 12 · 22:20 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 12 · 23:49 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 12 · 14:05 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 12 · 21:06 UTC
Between 12:54 and 21:06 UTC on October 12, 2026, Cloudflare experienced an issue that affected network performance in Seattle. During this time, customers may have experienced degraded network performance.
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 13 · 17:40 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 15 · 09:28 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 10 · 02:12 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 9 · 19:10 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 9 · 19:30 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 8 · 22:32 UTC
Cloudflare resolved an issue with network performance for our Sofia (SOF) facility which occurred today, 2026-10-08, from approximately 21:35 to 21:50 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 8 · 14:00 UTC
Cloudflare resolved an issue with network performance for our Kochi (COK) facility which occurred today, 2026-10-08, between approximately 14:00 and 17:00 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 8 · 17:00 UTC
Cloudflare resolved an issue with network performance for our Kochi (COK) facility which occurred today, 2026-10-08, between approximately 14:00 and 17:00 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 7 · 15:24 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 7 · 11:51 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 6 · 15:33 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 6 · 09:06 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 5 · 22:35 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 5 · 22:39 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 5 · 09:30 UTC
Cloudflare investigated reports of increased latency affecting requests for cacheable assets across multiple locations between 09:30 and 11:10 UTC. The issue is now resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 5 · 07:28 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 2 · 16:00 UTC
Between 17:11 and 17:22 UTC, Cloudflare experienced network performance degradation impacting Seoul, South Korea (ICN). The issue has been identified and fully mitigated, and network performance has returned to normal levels.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 2 · 21:57 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 14 · 16:54 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 5 · 00:00 UTC
Cloudflare identified an issue that affected Hyperdrive performance between 11th September and 5th October 2026. During this time, customers may have experienced elevated latency. This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗
resolvedOct 22 · 15:41 UTC
This incident has been resolved.
Reported by Cloudflare on their status page. View vendor report ↗