Who holds QUIC back?
HTTP/3 runs over QUIC, and most browsers and servers support it. Yet most requests to Cloudflare still use HTTP/2 or HTTP/1.1. This dashboard breaks down which parties account for the gap: bots, browsers, platforms, networks and countries. It uses live data from Cloudflare Radar.
The parties holding QUIC back
Who sends requests to Cloudflare without HTTP/3, computed live from the sections below. Each row compares a party's HTTP/3 share with the average for human traffic.
Bots barely use HTTP/3
HTTP versions used by human and automated traffic. Automated clients (crawlers, scripts, monitoring, API clients) mostly use HTTP/1.1 libraries without QUIC.
Browsers and platforms (human traffic)
HTTP/3 share of requests per group, derived with Bayes' rule from Radar's composition data. The vertical line is the best large group (≥ 3 % of traffic). Headroom is how many percentage points the overall HTTP/3 share would gain if that group used HTTP/3 as often as the benchmark.
Browser × operating system
HTTP/3 share per browser within each OS (human traffic). Stronger color means more HTTP/3; the number in each cell is the HTTP/3 share in percent. Cells with less than 0.5 % of the OS's traffic are left blank.
Networks
The 200 largest client networks (ASes) by human requests. Highlighted: the top 15 by the selected ranking. Low HTTP/3 shares in large networks point to UDP blocking or throttling, enterprise middleboxes, or unusual client mixes.
Countries
The 100 countries with the most human requests. Rank them by headroom (how much HTTP/3 the country holds back, which grows with its size) or by HTTP/3 adoption (lowest first).
Is the gap closing?
Weekly HTTP/3 share since 2023 (Radar's human/bot classification starts then).
Method and caveats
- Scope: only HTTP requests to Cloudflare's network. Radar can't see traffic to other CDNs or origins.
- Per-group rates: Radar only filters HTTP versions by bot class, device type, OS, location and network. Browser rates are derived as P(HTTP/3 | group) = P(group | HTTP/3) · P(HTTP/3) / P(group), from the browser mix of all requests and of HTTP/3 requests.
- Headroom is a what-if, not a measured loss. Part of every group's gap can't be closed by clients: sites that disable HTTP/3, first visits before the client learns about HTTP/3 (Alt-Svc / HTTPS records), and connections that are reused instead of upgraded.
- Benchmarks: for platforms, the best group with ≥ 3 % of traffic; for networks and countries, the traffic-weighted 75th percentile.
- Data: fetched live through a caching proxy (6 h) when you open the page. Cloudflare Radar data is licensed CC BY-NC 4.0.