Is it down for me?
Testing cloudflare.com from your device…
Most checked
Not listed? Type its address, like example.com, to check it now.
The official status page reports degraded service. Our last check from one location (UtiBox server · Newark, US) found it answering normally in 186 ms, so the website loads, but parts of Cloudflare may not be working.
Testing cloudflare.com from your device…
cloudflare.com loads, but the official status page reports degraded service. Total time to the final page on our latest check.
Thanks, you said it works
0 answers in the last 24 hours · 0 problem reports
One answer per person, counted for 24 hours.
No answers in the last 24 hours
Only our server so far. The regional checks run when the page opens.
No posts yet. Be the first to say how Cloudflare is working for you.
Our latest check, step by step. Tap a step to open its full record.
Our main check runs from Newark, US. Run the same test from up to 3 internet providers in another country to see whether cloudflare.com is blocked or broken there.
Press Ctrl + Shift + R (⌘ + Shift + R on a Mac).
Rules out extensions and stored cookies.
Move from Wi-Fi to mobile data, or the other way round.
Windows: ipconfig /flushdns · macOS: sudo dscacheutil -flushcache
They can block or reroute requests.
A wrong clock breaks secure connections.
| Date | Problem | Duration | Peak reports | Status |
|---|---|---|---|---|
| No confirmed incidents recorded for Cloudflare. | ||||
What people say about Cloudflare, in their own words, kept apart from our own checks.
Live counts · real numbers, refreshed with the page
Posts are public after a quick review. Don’t share personal details or links.
No posts yet.
Be the first to say how Cloudflare is working for you.
No posts of this type yet.
That’s every post from the last 30 days.
One answer per person, counted for 24 hours.
Having one of these? Tap it to start a report.
What Cloudflare status says about its own service, read from its public status page. A separate signal from our own check and from what people report.
Read from the official feed · the provider last updated it .
What Cloudflare status reports about Cloudflare’s products and services (not individual data centres). A site can answer our own check while the provider reports a problem with one of its features, and the other way round.
Status information is provided by the service operator. UtiBox is independent and isn’t affiliated with Cloudflare. It may not reflect regional or account-specific problems.
Minor impactupdated
A fix has been implemented and we are monitoring the results.
Minor impactupdated
The issue has been identified and a fix is being implemented.
Minor impactupdated
The issue has been identified and a fix is being implemented.
No maintenance is planned for Cloudflare’s products and services (not individual data centres) in the last report we read.
These don’t change the state above: the provider either listed them without an impact or didn’t tie them to Cloudflare’s products and services (not individual data centres).
13 Nov 21:00–23:00 UTC
We will be performing scheduled maintenance in HKG (Hong Kong) datacenter on 2026-11-13 between 21:00 and 23:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.
13 Nov 18:00–20:00 UTC
We will be performing scheduled maintenance in KIX (Osaka) datacenter on 2026-11-13 between 18:00 and 20:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.
13 Nov 17:00–19:00 UTC
Maintenance will begin soon as scheduled.
30 more notices on the official status page.
Our first successful read in this window was on 9 Nov 2026.
62 resolved updates since Oct 2026 · 2 major · last one 13 Nov 2026 (1 h 22 min)
“Cloudflare is investigating an elevated error rate for workers startup, for workers that use large amounts of memory We have identified the issue and are working on a solution to fix the issue. More updates to follow shortly.”
“Durable Objects saw an increased error rate in North American colos due to a sudden increase in traffic. Impact has subsided. We are now monitoring.”
“Cloudflare Replicate customers may see an increase of 500 errors for predictions. More updates to follow shortly.”
“Cloudflare is investigating issues with enabling or disabling DNSSEC (Domain Name System Security Extensions) signing. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.”
“We are aware of Network performance degradation near LAX and Western North America, we are working to resolve.”
“Cloudflare has identified and resolved an issue impacting Workers deployments with D1 bindings. Customers may have seen issues deploying their Workers between 12:42 UTC - 13:03 UTC 11th November 2026”
“Cloudflare is investigating an issue deploying a subset of Custom certificates. Customers are advised to temporarily pause certificate redeployments until this incident is resolved SSL certificates already in production remain unaffected and are operating normally.”
“Between 07:30-07:45 UTC customers reaching Hong Kong, may have experienced an elevated number of 5xx errors.”
“Cloudflare is aware of and investigating an issue with Cloudflare Worker Builds which potentially impacts multiple customers. Further detail will be provided as more information becomes available. Existing Workers and Containers are unaffected.”
“Cloudflare is investigating issues with Replicate input uploads. We are working to understand the full impact and mitigate this problem. More updates to follow shortly”
“Cloudflare is aware of, and investigating, an issue affecting predictions on official OpenAI models via Replicate. Customers may see that some predictions are failing with a 401 token_invalidated error. We are working to mitigate this problem. More updates to follow shortly.”
“Cloudflare is investigating an issue with Analytics filters on a subset of analytics dashboards.”
“Cloudflare is investigating issues with network performance in Eastern North America. We are working to analyse and mitigate this problem. More updates to follow shortly.”
“Cloudflare is aware of and investigating issues related to creating, editing and deleting Workers. Impact is limited to changing Workers — Workers that are already deployed are unaffected.”
“Cloudflare is investigating issues with Spectrum. This may be impacting the availability of existing Spectrum applications. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.”
“Between 04:55-05:12 UTC 7th Dec Cloudflare experienced issues with network performance in Chicago.”
“Cloudflare is investigating issues with Spectrum in Phoenix. This may be impacting the availability of existing Spectrum applications. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.”
“Cloudflare has identified a bug with our purge pipeline impacting fedramp customers. Stale content may be served until expired. Non-fedramp customers are not impacted.”
“Cloudflare is investigating an issue with Wrangler deployments, Pages, and Workers Builds. Users may observe from failed uploads. We are working to analyse and mitigate this problem. More updates to follow shortly.”
“Cloudflare is aware of and investigating an issue with Cloudflare Workers Builds which potentially impacts multiple customers. Further detail will be provided as more information becomes available.”
“Network disruption across multiple colocations in India, impacting Cloudflare services in region”
“Cloudflare investigated an issue that caused an increase of errors for Durable Objects in Western Europe. The issue has been resolved and we are monitoring the results.”
“Cloudflare has resolved an issue affecting Durable Objects and downstream services in the Eastern North America (ENAM) region. Some customers may have seen elevated errors between approximately 21:20 and 21:22 UTC on November 4, 2026. This also affected downstream services such as R2.”
“We are currently investigating a network latency issue in NRT”
“Cloudflare is aware of and investigating an increased number of errors from Durable Objects in Dallas, Texas, USA. More updates to follow.”
“Cloudflare is aware of and investigating an issue with Cloudflare Workers and Pages build failures which potentially impacts multiple customers. Further detail will be provided as more information becomes available.”
“Cloudflare has resolved an issue affecting R2 and downstream services in the Western North America region. Some customers may have seen elevated latency and errors between approximately 13:00 and 22:15 UTC on November 3, 2026. This may also have affected downstream services such as Stream and Pipelines.”
“Between 06:20-6:32 UTC customers reaching Hong Kong may have experienced an elevated number of 5xx errors or CNI timeouts due to congestion.”
“Cloudflare is investigating an increased level of errors for Containers failing to start. We are working to analyse and mitigate this problem. More updates to follow shortly.”
“Cloudflare is investigating issues with Network Performance in the APJC region. We are working to analyze and mitigate this problem. More updates to follow shortly.”
“Cloudflare is investigating an issue affecting Cloudflare Gateway DNS-over-TLS (DoT) connections over IPv4. Affected customers may experience connection timeouts and failed DNS resolution. This issue is limited to DoT over IPv4. DoT over IPv6, DNS-over-HTTPS (DoH), and standard DNS over UDP/TCP are not affected. We are working to identify the cause and restore connectivity. Further updates will be provided as more information becomes available.”
“Some customers may see delays when deploying updates to Cloudflare Workers. Remediation is in progress.”
“Cloudflare is observing cache purge delay in Qingdao in Shandong, China. We are working to resolve this issue as soon as possible. More updates to follow.”
“Cloudflare is aware of, and investigating an issue with Browser Run which potentially impacts multiple customers. Customers may see intermittent 500 errors when trying to use Browser Run Quick Actions. We are currently investigating this issue.”
“Cloudflare is investigating elevated latency affecting R2 requests in Eastern Europe. We are actively investigating and will provide further updates as soon as more information becomes available.”
“Cloudflare has identified the cause of increased errors affecting Durable Objects and downstream services in the Eastern North America (ENAM) region. We are working to implement a fix.”
“Cloudflare is investigating an issue where customers are experiencing elevated errors for operations on Increased Durable Objects, D1 and Workflows.”
“We are currently investigating reports of increased HTTP 429 (Rate Limit Exceeded) errors impacting users accessing dash.cloudflare.com. This issue primarily affects legitimate users connecting via shared egress networks (such as Cloudflare One default egress IPs or external corporate proxies). Our engineering team is actively investigating the root cause and adjusting rate-limiting thresholds to restore normal dashboard access.”
“Cloudflare is investigating issues causing degraded availability and elevated error rates for Durable Objects in Eastern Europe (EEUR2 region). Customers using Durable Objects or dependent services may experience increased errors or latency. We are actively investigating and will provide further updates as soon as more information becomes available”
“Cloudflare has identified an issue where customers are experiencing elevated 500 errors impacting Durable Objects, D1, Workflows, Workers Assets uploads and Cloudchamber.”
“Cloudflare is aware of and investigating an issue affecting Cloudflare Network Interconnect (CNI) 2.0 traffic in LAX (Los Angeles). Some CNI 2.0 customers with traffic in this location may observe increased errors and/or latency on their connections.”
“Cloudflare is investigating increased error rates and latency for R2 in ENAM region.”
“Cloudflare is aware of, and investigating an issue with Durable Objects and downstream services which potentially impacts multiple customers in the Eastern North America region. Durable Objects in the region may experience increased error rates, and elevated errors for storage operations. This may also affect downstream services such as D1, Queues and Workflows etc. We are currently investigating this issue.”
“Cloudflare is aware of, and investigating an issue with Durable Objects and downstream services which potentially impacts multiple customers in the Eastern North America region. Durable Objects are experiencing an elevated level of overload errors in the aforementioned region. This may also affect downstream services such as D1, Queues and Workflows etc. We are currently investigating this issue.”
“Beginning approximately 19:30 UTC, Network Error Logging (NEL) reports are not being processed. Reports received during this period will not appear in Network Error Logging analytics. Website traffic and other services are not affected. We are investigating and will provide an update as soon as possible.”
“The Cloudflare engineering team is investigating an elevated level of Access api errors. This may result in configuration update failing or being delayed. Authentication and policy enforcement are not impacted at this time.”
“We are currently investigating an issue that is causing intermittent failures in unsafe topic detection within AI Security for Apps.”
“Cloudflare Stream is investigating degraded playback of certain live broadcasts originating from Western Europe and long processing times for on-demand video uploads.”
“Some single-file cache purge requests (purge by URL) submitted through the Dashboard or API and routed through our EEUR purge queues are experiencing delays of up to 30 minutes. Cache invalidation for these requests may be delayed across our global network. This also affects Always Online. We are working to resolve the issue. As a temporary workaround, you may use Purge Everything, but this may cause a surge in traffic to your origin server(s) More updates to follow.”
“Cloudflare has identified an issue affecting customers whose traffic passes through an external vendor firewall. Customers may observe: ERR_TIMED_OUT on standard HTTPS websites ERR_EMPTY_RESPONSE on non-standard HTTPS ports (e.g., 8443) We're investigating to confirm the root cause and possible fixes.”
“Cloudflare has identified an issue impacting some Workers Builds customers where we would fail to deploy Workers with Containers. We are working to mitigate the problem. More updates to follow shortly.”
“We are currently investigating an issue where some customers may notice their Pages and/or workers builds are intermittently failing.”
“We are investigating reports that some Workers Cron Triggers are running late, being skipped, or running more than once. Affected customers may see scheduled Workers invocations that do not run on time or run more than once. We will post an update as we learn more.”
“Cloudflare is investigating increased delays running Workers builds. We are working to analyse and mitigate this problem. More updates to follow shortly.”
“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.”
“Between 2026/10/26 - 2026/11/4, some customers trying to upload static Pages assets from the Cloudflare Dashboard may have experienced issues creating a Pages project.”
“Cloudflare is investigating issues causing an increase of errors for Workflow Operations. We are working to analyze and mitigate this problem. More updates to follow shortly.”
“Cloudflare is investigating issues with Network Performance in Ashburn, VA. We are working to analyze and mitigate this problem. More updates to follow shortly.”
“We are investigating degraded network performance affecting some traffic between our Ashburn and Atlanta data centers. Some customers may see increased latency, packet loss, or intermittent errors on Workers and other services in the Eastern US. Our network team is actively working on mitigation.”
“We are investigating reports that some Workers Cron Triggers are running late, being skipped, or running more than once. Affected customers may see scheduled Workers invocations that do not run on time or run more than once. We will post an update as we learn more.”
“Our helpdesk provider is currently experiencing issues, and as such customers might encounter errors while submitting or viewing tickets. Responses on customer inquiries may be delayed during this time.”
“Between October 5 at 1:00 PM UTC and October 23 at 9:00 PM UTC, some customers may have experienced missing log events, incomplete traces, or inconsistent issue counts due to ingestion pipeline capacity limits. Traffic and Workers were not affected, and customers will not be billed for dropped events. Capacity has since been increased, and service has returned to normal.”
No updates of this kind.
From Cloudflare status’s public status history. UtiBox keeps the official updates it reads for 180 days.
At our last check from UtiBox server · Newark, US, Cloudflare was up and answering normally. The official status page reports degraded service on its status page, though, so parts of Cloudflare may not be working even though the website loads. The page refreshes the check automatically.
The official status page (www.cloudflarestatus.com) reports “Degraded” for Cloudflare’s products and services (not individual data centres), with 3 open incidents. We read it every few minutes. It’s separate from our own check of the cloudflare.com website above, so the two can differ.
If it’s up here but not for you, the problem is usually local: your connection, DNS, a browser extension, a VPN or a block on your network. Try the fixes on this page, then the Is It My Internet? check.
Our server requests cloudflare.com and looks at every layer: DNS, the connection, the TLS certificate, the HTTP answer, redirects and the page content. We also check it from up to 12 locations in other countries, using two free probe networks (Globalping and check-host.net), so a regional outage can show here too.
A result is shared for 60 seconds when the site is up and 30 seconds when it has problems, then checked again. You can refresh it yourself after 30 seconds.
Yes. Use “Alert me when it’s back” and we’ll send one email when our check reaches it again. Guests confirm their address first.
UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.
Keep forms secure (ubsid) and remember that you’ve seen this notice (ub_consent). Things you ask us to remember, like light or dark mode and closed banners, are part of this.
UtiBox is free because of ads. Google AdSense and its partners use cookies to show, limit and measure ads. To change how Google personalises the ads you see, use Google’s My Ad Center. To opt out of personalised ads from many companies, visit aboutads.info or youronlinechoices.eu.
Google Analytics counts visits and shows us which pages and tools people use, so we can improve them. It sets _ga cookies. In the EEA, the UK and Switzerland it stores nothing unless you agree. To opt out on any site, use Google’s opt-out browser add-on. Ahrefs Web Analytics counts visits without cookies: it stores nothing on your device and never keeps your IP address; block analytics.ahrefs.com to opt out. Microsoft Clarity records clicks and scrolling for heatmaps and replays, with the tool area and what you type blanked out; block clarity.ms to opt out.