Cloudflare Reaches Fastest Provider Status in 74% of Top Global Networks

Cloudflare Reaches Fastest Provider Status in 74% of Top Global Networks In its 2026 Birthday Week update, Cloudflare reported becoming the fastest provider in 74% of the world's top 1,000 networks, expanding its lead by integrating real-user performance tests into Cloudflare Challenge Pages. Cloudflare is the fastest provider in 74% of the top 1,000 networks globally, rising from 60% in April 2026 with gains across 150 networks and 38 countries. Performance is evaluated using TCP connection time trimeans against competitors including Amazon CloudFront, Google, Fastly, and Akamai. Data collection expanded from branded error pages to include non-interactive background measurements on select free Cloudflare Challenge Pages powered by Turnstile. Higher test volumes reduce statistical noise and daily ranking volatility where competitors differ by only 1 to 2 milliseconds. Global Performance Growth Cloudflare's ranking among the 1,000 largest global networks—identified via APNIC user population data—rose by 14 percentage points from April to August 2026. The increase to 74% represents the fastest speeds in an additional 150 top networks and 38 additional countries, evaluated using user connection times on networks serving the largest populations. Measurement via Error and Challenge Pages To gauge real-world conditions, Cloudflare measures TCP handshake connection times using a trimean weighted average across the 25th, 50th, and 75th percentiles. Alongside historical tests from error pages, Cloudflare introduced background measurements on Turnstile-powered Challenge Pages. These run lightweight file fetches from Cloudflare, CloudFront, Google, Fastly, and Akamai without requiring visitor interaction or degrading performance. Data Resolution and Ranking Stability Adding Challenge Pages increases measurement volume and geographic diversity across networks. In close competitions where top providers are separated by 1 to 2 milliseconds, the increased sampling narrows confidence intervals, prevents day-to-day fluctuations from altering rankings, and provides a more stable evaluation of which provider is genuinely fastest.

Cloudflare发布2026年生日周网络性能更新：全球前千大网络最快比例升至74% Cloudflare在2026年生日周宣布，其在全球前1,000大网络中成为最快提供商的比例已达74%，并公布了结合挑战页面（Challenge Pages）的全新真实用户性能测量方法。 Cloudflare在全球前1,000大网络中最快的占比从2026年4月的60%上升至8月的74%，在150个新增网络和38个新增国家中登顶。 性能评测基于APNIC排名的网络，以TCP握手连接时间为基准，并使用三均值（trimean）加权平均来降低异常值干扰。 测量数据收集从原有的Cloudflare品牌错误页面拓展至免费版挑战页面，在不影响用户体验的前提下大幅扩充了网络测试广度与样本量。 性能突破与网络覆盖进展 依据APNIC估计用户规模排名的全球前1,000大网络中，Cloudflare作为最快提供商的比例由2026年4月的60%增长14个百分点至8月的74%。这一提升相当于在上述前千大网络中额外赢得了150个网络，并在38个新增国家中排在首位。评估所依据的核心指标为完成TCP握手所需的连接时间，并采用综合第25、50和75百分位数的加权三均值（trimean）进行供应商排序，以如实体现大部分用户的常规体验并削弱极端值干扰。 基于挑战页面的新测量方法 自2021年以来，Cloudflare主要利用品牌错误页面在后台静默获取轻量测试数据，对比Cloudflare、Amazon CloudFront、Google、Fastly和Akamai等服务商的连接表现。为进一步提升数据质量与覆盖范围，官方新增了通过Cloudflare挑战页面（Challenge Pages）收集性能指标的机制。测试仅在部分符合条件的免费挑战页面后台静默运行，拉取轻量测试文件并记录连接耗时，既不增加显著延迟，也保留了Turnstile的隐私特性，使数据收集更广泛地覆盖真实日常访问环境。 数据规模化提升排名分辨率与稳定性 测量规模的扩大有效解决了竞争胶着网络的排名波动问题。在许多网络中，头部服务商之间的三均值连接时间差距仅为1至2毫秒（例如50毫秒与51毫秒），日常轻微波动极易导致排名颠倒。新方法带来了更多网络样本与测试量，收窄了统计置信区间，从而将真实性能优势与统计噪声区分开来，使网络性能排名的呈现更为稳定和客观。

Cloudflare is now the fastest provider in 74% of the 1,000 largest networks around the world, [up from 60%](https://blog.cloudflare.com/network-performance-agents-week/) in April 2026. This huge improvement matters because every millisecond affects how quickly users can reach the applications, APIs, and websites they rely on. In this Birthday Week performance update, we’ll review how we get our measurements, introduce a new measurement methodology using Cloudflare Challenge Pages, and discuss where these improvements have had the biggest impact for customers. In August, Cloudflare was the fastest provider in 74% of top networks, up 14 percentage points from our last update during Agents Week in April. The figure below shows the countries where Cloudflare is the fastest provider. We improved from 60% to 74% by becoming the fastest provider in an additional 150 networks out of that top 1,000, and there are 38 additional countries where Cloudflare now ranks as the fastest. We measure this by looking at the fastest provider for users on the networks serving the largest number of users in each country. The graphic below shows countries where Cloudflare has become the fastest provider across those networks since April. Here you see the number of additional networks on which Cloudflare is now the fastest. Our analysis begins with the 1,000 largest networks in the world, ranked by estimated user population using data from [APNIC](https://stats.labs.apnic.net/cgi-bin/aspopjson). Because these networks cover users across a wide range of geographies and access environments, they give us a useful view into how people actually experience the Internet. For each network, we evaluate performance using connection time: the amount of time required for a user’s device to complete a TCP handshake when requesting content. We use this because it maps closely to what people think of as a “fast” user experience. It reflects real-world factors such as distance, routing, and congestion, while still being specific enough for us to compare providers and identify where performance can improve. To rank providers, we calculate the trimean of connection times. The trimean combines the 25th percentile, 50th percentile, and 75th percentile into a weighted average. Using this method helps reduce the influence of unusual outliers while still representing the range of experiences that most users see. You can read [previous posts](https://blog.cloudflare.com/introducing-radar-internet-quality-page/) to learn more about why we chose this metric. When someone reaches a Cloudflare-branded error page, their browser can run a small background measurement that fetches lightweight files from several providers, including Cloudflare, Amazon CloudFront, Google, Fastly, and Akamai. We then record how long each connection takes from that user’s browser, on that user’s network, at that moment. This gives us a picture of performance under real Internet conditions, not just in controlled test environments. Since 2021, Cloudflare-branded error pages have provided a reliable source of real-user performance data, and they remain an important part of how we measure performance. But measurement gets better with scale. The more data we collect, and the more networks we observe, the more accurately we can understand how users experience the Internet. Since our last update, we have expanded our performance data collection by adding measurements using Cloudflare Challenge Pages. If you're not already familiar, Cloudflare Challenge Pages are full-page screens that verify visitors before they reach a website. When a challenge is actioned — typically by a Web Application Firewall rule — the Challenge Page acts as a gate: it holds the request, evaluates the browser environment for automated signals, and only lets legitimate visitors through, usually with no interaction required. Challenge Pages are delivered by [Cloudflare Turnstile](https://www.cloudflare.com/products/turnstile/), our privacy-preserving, risk-based challenge technology that runs directly in the visitor's browser. Because Challenge Pages run across a broad set of websites and real-world network conditions, they present a novel way to collect performance measurements from the places where people actually use the Internet. If you want to add Challenge Pages to your own website, you can get started with the [Cloudflare Challenge Pages documentation](https://developers.cloudflare.com/cloudflare-challenges/challenge-types/challenge-pages/). From an end user's perspective, Challenge Page-based measurement works much like our existing error-page measurements: it runs quietly in the browser and does not require the user to do anything extra. While the visitor is on a Challenge Page a small, non-interactive measurement runs in the background. It fetches lightweight files from a fixed set of endpoints, including Cloudflare, Amazon CloudFront, Google, Fastly, and Akamai, and records whether each request completed and how long it took. While we care about measuring performance, we care even more about improving it. That includes making sure our measurements do not negatively affect the user experience. We designed the Challenge Page measurement to avoid adding noticeable latency for visitors, while preserving the privacy-focused properties that Turnstile brings to Challenge Pages and that make them different from traditional CAPTCHAs. For now, we are running measurements on only a small fraction of eligible free Challenge Pages, in addition to continuing to collect data from Cloudflare-branded error pages. We will limit these measurements to free Challenge Pages and we will only increase the sampling rate if the additional data improves measurement quality and end-user performance remains unaffected. The main upgrade from the error-page method alone is reach. Cloudflare-branded error pages have given us high-quality measurements from a narrower set of use cases, while Challenge Pages let us collect similar measurements during everyday interactions, wherever a challenge is already being served. That means more measurements from more networks, without requiring users to take any additional action. By collecting measurements on Challenge Pages, we are dramatically increasing the volume of data we collect and improving the diversity of users, networks, and geographies we measure. From a data quality perspective, this takes an already informative dataset to the next level. Even though the initial results from Challenge Pages measurements are promising, we have even more ideas for how to improve the dataset. First, we want our measurements to describe the experience of as many users as possible. Because Challenge Pages runs across such a broad set of websites and visitors, it gives us measurements from networks well beyond the top 1,000 and far more samples within each one, especially as we increase our test volume. That breadth gives us more analytical options: we can explore views that a network-count ranking alone cannot support, such as weighting performance by the number of people who experience it, grouping results by country or worldwide instead of by network, and quantifying how much of total user traffic our measured networks represent. Second, more measurements give us sharper resolution where the race is closest. In many networks, the top providers are separated by only a millisecond or two of trimean connection time such as Cloudflare at 50 ms and Fastly at 51 ms, which is a gap small enough that ordinary day-to-day variation can flip the ranking. As Challenge Pages add measurement volume, the confidence interval around each provider's trimean will narrow, letting us distinguish a genuine lead from statistical noise. The results we are sharing today are early, but as the dataset becomes larger, we expect future movement in these rankings to further reflect real changes in performance. This significant improvement coincides with the addition of our new measurement methodology described above. By increasing measurement volume, Cloudflare has more opportunities to compare performance against other top providers across a broader set of networks and user conditions. In practice, this gives us a clearer signal in networks where performance among top providers is very close. For example, Cloudflare may have previously ranked second in some networks even though our trimean connection time was only 1 or 2 ms slower than the fastest provider. With more measurements, the results are less sensitive to outliers and day-to-day variation. That makes rankings more stable, especially in countries and networks where the fastest provider may have previously changed from one day to the next. As the dataset becomes larger and more representative, we get a more consistent view of which provider is actually fastest in each network. Improving performance is a continuous process, and so is improving how we measure it. This year’s results show meaningful progress: Cloudflare is now the fastest provider in 74% of the top networks we measure, and our new Challenge Pages-based methodology gives us a broader, more stable view of Internet performance around the world. We’ll keep using that data to find where we can be faster, validate the impact of our improvements, and make the Internet better for the customers and users who rely on Cloudflare every day. Follow our blog for more [performance updates](https://blog.cloudflare.com/tag/network-performance-update/) as we continue to make the Internet faster.