Among European Companies That Use a CDN, Nearly 9 in 10 Use Cloudflare
Among European Companies That Use a CDN, Nearly 9 in 10 Use Cloudflare
在使用 CDN 的欧洲公司中，近 90% 使用 Cloudflare
A content delivery network sits in front of a website. Requests hit the CDN’s edge servers first, which serve cached content, terminate TLS, filter traffic, and pass the rest back to the origin. That means the CDN is a shared dependency: if it goes down, every site behind it goes down together, whether or not those sites have anything else in common.
内容分发网络（CDN）位于网站的前端。请求首先到达 CDN 的边缘服务器，由其提供缓存内容、终止 TLS、过滤流量，并将剩余请求传回源站。这意味着 CDN 是一种共享依赖：如果它宕机，其背后的所有网站都会同时瘫痪，无论这些网站之间是否有其他共同点。
I went through CipherCue’s tracked European companies to see which CDN fronts their websites. Of the 44,143 companies where we detected a CDN at all, 39,547 are behind Cloudflare. That is 89.6%.
我查阅了 CipherCue 追踪的欧洲公司数据，以查看哪些 CDN 为其网站提供前端服务。在我们检测到使用 CDN 的 44,143 家公司中，有 39,547 家位于 Cloudflare 之后，占比为 89.6%。
For a reference point, W3Techs put Cloudflare at 84.1% of sites where the reverse proxy provider can be identified, as of 28 July 2026. Our 89.6% is measured the same way, as a share of the identified set rather than of all sites, so the two are close; the European cut here runs a little higher. I only counted companies that actually run a CDN. If a company serves its site straight from its own origin, it is not in these numbers at all. So this is not “Cloudflare vs the entire web”; it is who the CDN users went with.
作为参考，截至 2026 年 7 月 28 日，W3Techs 的数据显示，在可识别反向代理提供商的网站中，Cloudflare 的占比为 84.1%。我们的 89.6% 采用同样的衡量方式，即在已识别集合中的占比而非所有网站的占比，因此两者非常接近；欧洲市场的这一比例略高。我只统计了实际运行 CDN 的公司。如果一家公司直接从其源站提供服务，则不计入这些数字。因此，这并非“Cloudflare 对抗整个互联网”，而是 CDN 用户选择了谁。
First place and everyone else
第一名与其他竞争者
The four CDN vendors we classify, counted as distinct companies where each was detected: 我们分类的四家 CDN 供应商，按检测到的不同公司统计如下：
- 39,547 Cloudflare
- 3,112 Amazon
- 1,299 Fastly
- 396 Akamai
Amazon is second at 3,112, but that number needs a caveat. We detect Amazon through CloudFront, and Amazon is also a general cloud host, so some of these are companies whose origin happens to sit on AWS rather than companies that deliberately chose CloudFront as their front door. Fastly does not have that ambiguity. It is a pure CDN, and it comes third at 1,299, which is roughly one company for every thirty behind Cloudflare. Akamai, the oldest name in the category, is fourth at 396.
亚马逊以 3,112 家位居第二，但这个数字需要说明。我们通过 CloudFront 检测亚马逊，而亚马逊同时也是一家通用云主机提供商，因此其中一些公司只是因为源站恰好位于 AWS 上，而非刻意选择 CloudFront 作为前端。Fastly 则没有这种歧义。它是一家纯粹的 CDN 提供商，以 1,299 家位居第三，大约是 Cloudflare 背后公司数量的三十分之一。该领域最老牌的 Akamai 以 396 家位居第四。
Per country
各国情况
Rolling eight countries into one figure hides the differences between them, so here is the same measurement per country. Cloudflare is the majority front door in all of them, but the share ranges from about four in five in Spain and Ireland to about nineteen in twenty in the Netherlands.
将八个国家的数据汇总为一个数字会掩盖它们之间的差异，因此以下是按国家/地区划分的相同测量结果。Cloudflare 在所有这些国家中都是主要的前端入口，但其份额从西班牙和爱尔兰的约五分之四，到荷兰的约二十分之十九不等。
| Country | Companies with a CDN | Behind Cloudflare | Cloudflare share |
|---|---|---|---|
| Netherlands | 7,939 | 7,587 | 95.6% |
| United Kingdom | 17,007 | 15,846 | 93.2% |
| Poland | 2,896 | 2,682 | 92.6% |
| France | 4,008 | 3,456 | 86.2% |
| Italy | 3,661 | 3,126 | 85.4% |
| Germany | 5,715 | 4,650 | 81.4% |
| Spain | 2,001 | 1,576 | 78.8% |
| Ireland | 792 | 624 | 78.8% |
What the concentration costs
市场集中的代价
Part of why a company buys a CDN is resilience, and one advantage of independent suppliers is that they fail independently. That advantage disappears when most of a market is behind the same supplier. An incident there is no longer one company’s outage; it is most of the market’s outage, on the same afternoon.
公司购买 CDN 的部分原因是出于弹性考虑，而独立供应商的一个优势在于它们会独立发生故障。当市场上的大多数公司都使用同一家供应商时，这种优势便荡然无存。一旦发生事故，就不再是一家公司的宕机，而是整个市场在同一个下午的大规模瘫痪。
Cloudflare has published postmortems for several incidents in the last fifteen months. None of the three was an attack. A doubled config file, a change made while patching someone else’s vulnerability, a cleanup job that deleted too much: routine internal work that reached the edge and took a lot of sites down with it. The companies in the table did not need anything in common to go offline together on 18 November. Sharing a front door was enough.
Cloudflare 在过去十五个月中发布了多起事故的事后分析报告。其中三次事故均非攻击所致。无论是重复的配置文件、在修补他人漏洞时进行的更改，还是删除了过量数据的清理任务，这些常规内部工作触及边缘服务器后，导致了大量网站瘫痪。表中的公司在 11 月 18 日集体下线，它们之间无需任何共同点，仅仅因为共享同一个前端入口就足够了。
This is not about Cloudflare being sloppy. Fastly and Akamai ship bugs like this too; theirs just take fewer sites down because fewer sites are behind them. That is the whole point. When one provider fronts most of a market, its mistakes stop being its own problem and become everyone’s, at the same time.
这并不是说 Cloudflare 工作草率。Fastly 和 Akamai 也会出现类似的 Bug；只是因为它们背后的网站较少，所以受影响的范围也较小。这正是问题的关键所在。当一家供应商占据了市场的大部分前端时，它的错误就不再仅仅是它自己的问题，而会同时成为所有人的问题。
The CDN is not where the data lives
CDN 并非数据存储地
This says nothing about where a company keeps its data. The CDN is just the front door; the origin server, the database, and whoever processes the data sit behind it, and for a GDPR or data-residency question that back end is what counts. Measure that instead and Europe looks better: people who dig into API subdomains rather than the front door usually turn up far more OVH and Hetzner than I see here.
这并不代表公司将数据存储在哪里。CDN 只是前端入口；源服务器、数据库以及处理数据的后端才是关键，对于 GDPR 或数据驻留问题，后端才是重点。如果测量后端，欧洲的情况会好得多：深入研究 API 子域名而非前端入口的人，通常会发现比我这里看到的更多的 OVH 和 Hetzner。
Check your own front door
检查你自己的前端入口
You can see which CDN, if any, fronts a domain from its response headers: 你可以通过响应头查看某个域名是否使用了 CDN 以及使用了哪家 CDN：
curl -sI https://example.com | grep -i 'server\|cf-ray\|x-served-by\|x-amz-cf-id'
A cf-ray header or server: cloudflare indicates Cloudflare.
cf-ray 响应头或 server: cloudflare 表示使用了 Cloudflare。