CDN on Russian websites in 2026: rarer, and not Cloudflare

Numbers here come from two places and are kept apart.

An independent survey, cited with its date. It counts the whole web and does not describe the Russian segment separately.

Our own measurement. On 27 August 2026 we requested headers from domains users had brought to our tools — 90 per zone. 61 answered in .ru and 60 in .com; the rest never opened a connection. A CDN was identified two ways: from response headers (cf-ray, x-amz-cf-id, x-fastly-*, server: ddos-guard, qrator and similar) and, when the headers were silent, from the owner of the IP address. Of the 15 hits in .ru, ten came from headers and five from address ownership; in .com, 28 and 9.

This is not a sample of the Russian web: these domains reached us because somebody chose to check them. Comparing the zones to each other is sound — they were collected the same way — but the level cannot be carried over to "all websites".

As of August 2026, W3Techs reports Cloudflare serving 84.5% of the sites whose reverse proxy can be identified at all — 24.9% of every website on the internet.

That figure describes the web as a whole, where the overwhelming majority of sites are not Russian. What follows shows how far the picture moves once you look at .ru domains.

A two-and-a-half-fold gap, and it holds whichever way the CDN was identified — headers or address ownership.

Worth noting separately: 22 domains in .ru and 27 in .com never opened a connection within the eight seconds allowed. They count in neither the numerator nor the denominator — "did not answer" is not "has no CDN".

The gap in adoption is not the interesting part. What matters is who serves the sites in each zone:

In .ru the top three are Russian companies — DDoS-Guard, Selectel, Qrator — while Cloudflare, which holds 84.5% of the identifiable web according to W3Techs, appears once in fifteen. In .com it takes nearly half the hits.

This is not "the Russian web fell behind": CDNs are available, they simply come from different suppliers. Note the composition too — DDoS-Guard and Qrator are attack mitigation first, with faster delivery as a side effect. A Russian site more often arrives at a CDN fleeing a threat than chasing speed.

1. Check whether you already have one. The signal sits in the response headers, which the HTTP header checker shows, and the address owner is visible through IP lookup.
2. Do not conflate a CDN with attack protection. The Russian services in the top three solve the second problem first. If you need delivery speed, look at where the points of presence are, not at the brand.
3. Measure rather than assume. A CDN does not always help: if the bottleneck is your server’s response rather than the road to the visitor, the gain is invisible. Start with a speed check and time to first byte.
4. Account for the dependency. A site behind a CDN is unreachable when the CDN is. Uptime monitoring will tell you before your customers do.