· 7 min read

Is Cloudflare Blocked in Russia in 2026? A First-Hand Test

Short answer: partially. DPI throttling breaks TLS on many Russian ISPs. What users actually see, who should keep Cloudflare, and CDN alternatives that work.

When you build a site for a Russian B2B audience in 2026, the CDN question is ‘Cloudflare or not’. Cloudflare became the default outside Russia, but inside the country the last 18 months added problems - ISP-level blocking, DPI, unstable speed. On my project I picked Beget CDN. Here’s why and who it fits.

In brief

  • Cloudflare gives CDN + DDoS protection + WAF + DNS - a lot of useful ‘out of the box’.
  • In Russia 2024-2025: parts of IP range blocked, DPI breaks SSL handshake, some users see the site slowly or not at all.
  • For local B2B that’s critical: every percent of lost users is money.
  • Alternatives for a Russian audience: Beget CDN (if you host there), Yandex Cloud CDN, Selectel CDN.
  • I picked Beget CDN - built into hosting, no DNS migration, no regulatory risk.

What Cloudflare gives

Cloudflare isn’t a pure CDN - it’s a stack of infrastructure services:

  • CDN - serving static (CSS, JS, images) from edge nodes worldwide. When a user in Paris opens your site, they get the CSS from a Paris edge, not from your server in Moscow.
  • DDoS protection at L3/L4 (network) and L7 (application) layers. Free even on the free plan.
  • DNS - Cloudflare became one of the largest DNS providers. The 1.1.1.1 resolver is theirs.
  • WAF - request filtering at the application layer, protection against SQL injection, XSS, exploit databases.
  • Workers - serverless edge compute (running JS/Wasm code near the user).
  • R2 - S3-compatible storage.

For a global SaaS company or an information site with a worldwide audience, this is very convenient. One service covers a heap of tasks, and the free plan is actually free and works.

What changed in Russia in 2024-2025

Since spring 2024 Russian ISPs have been blocking parts of the Cloudflare IP range via DPI (deep packet inspection). It’s not a ‘full domain block’ but targeted interference: TLS handshake stalls for 5-10 seconds or fails. The user doesn’t see ‘site blocked’ - they see ‘page slow to load’ or ‘connection failed’. In 80% of cases they close the tab.

What matters: the blocks are asymmetric. They depend on the ISP, the region, the time of day. A user in Moscow on MTS opens the site in 800 ms; their neighbour on Beeline takes 12 seconds; a third on corporate VPN sees it fine. You can’t reproduce it stably, so the problem is hard to debug.

For a global site where Russia is 5-10% of traffic, that’s tolerable. You can lose a specific Russian client, but the loss mass isn’t critical. For a local B2B site (cleaning in St. Petersburg, furniture in Moscow, renovation in Yekaterinburg) - every percent has a price in rubles. And here Cloudflare works against you.

What I picked instead

The site’s main audience is Russia, with focus on St. Petersburg and Moscow. Cloudflare stack goals:

  • CDN for static - needed, but in the Russian zone
  • DDoS protection - not needed, small B2B isn’t an attacker target
  • WAF - covered by server-side filters (see the form anti-spam article)
  • DNS hosting - needed, but not critical where from
  • Workers / R2 - not needed in my stack

Choice among Russian CDNs:

Beget CDN - built into Beget hosting. Free with the existing plan, servers in Moscow, St. Petersburg, regions. Speed on Russian audience - excellent. Downside: feature limits (no WAF Cloudflare-style, no Workers), but I don’t need them.

Yandex Cloud CDN - a production service from Yandex, Russian edge nodes, billing by outbound traffic volume. You set it in front of your backend, configure cache rules. Fits if you have a large site with its own infrastructure stack. Current prices and regions - on the service page.

Selectel CDN - similar to Yandex Cloud. Russian servers, flexible caching rules, transparent billing.

No CDN at all - for small sites with traffic up to 1000 uniques a day. Server serves everything directly, browser cache + correct Cache-Control covers most tasks. A legitimate option if your hosting is fast and the audience is mainly in Russia.

I picked Beget CDN because:

  1. I already host there - no new accounts, billing, DNS migration.
  2. Free. Any ‘extra cost’ at this project stage is excess.
  3. Servers in Russia, speed for the St. Petersburg audience is excellent.
  4. I don’t change NS records - kept them at the domain registrar; only the CDN layer goes through Beget.
  5. When I want to turn CDN off for half an hour (for debugging or cache reset) - one button in the panel.

What Beget CDN doesn’t cover

So as not to leave the impression ‘Russian CDN is a silver bullet’, honestly about the downsides:

Fewer edge nodes. Beget is mainly Moscow and St. Petersburg. Yandex Cloud adds Siberia and Vladivostok. Cloudflare has hundreds of nodes worldwide. If your audience is in 50 countries - no way without a global CDN.

Fewer features. WAF, bot management, custom cache rules - either absent or stripped down. Large sites that seriously tweak config won’t sit on Beget CDN.

Dependence on the host. If you decide to move from Beget to another host - you’ll have to migrate the CDN in parallel. In Cloudflare scenarios hosting and CDN are independent.

No global DNS. My DNS lives at the registrar (REG.RU). On Cloudflare you could move DNS there too and get TTL 5 minutes for changes - convenient for tests. At registrars TTL is usually an hour or two.

When I do leave Cloudflare

I don’t remove CF for every client. Scenarios where it stays:

  • Global SaaS or e-commerce. If a client has 60% US traffic, 20% Europe, the rest worldwide - Cloudflare is fine. The Russian audience gets ‘as is’.
  • A site with a real DDoS history. If the site really is attacked (media, politics, competitive niche) - Cloudflare DDoS protection is free and works. Russian CDNs don’t provide such protection in free mode.
  • A global B2B startup. Development straight onto the international market, RU audience not a priority - leave CF, don’t touch.

For a small Russian B2B services site - Cloudflare is more of a minus than a plus in 2026. Not an ideology of ‘Russian is better’, but a sober assessment of the infrastructure landscape.

If you’ve decided to migrate from CF to a Russian CDN

The migration scenario is roughly this:

Step 1: at the domain registrar side, change NS records from Cloudflare to NS of your hosting provider (Beget, Reg.ru, Yandex Cloud). DNS will update in 4-24 hours.

Step 2: on the hosting panel side, enable CDN. At Beget it’s a checkbox in the ‘Sites’ section. At Yandex Cloud - creating a Resource in Cloud CDN with origin set to your hosting.

Step 3: check the response headers. Static resources should show X-Cache: HIT or equivalent.

Step 4: test on different ISPs (MTS, Beeline, corporate network) - speed should become even, without delay spikes.

Step 5: watch Search Console and Yandex Webmaster. Sometimes a hosting IP change triggers a temporary authority recompute. In 90% of cases - invisible, in rare cases - position drops for 2-3 weeks, then returns.

The full case for launching a hand-coded site on shared with PHP - in the article ‘50 days of SEO in B2B cleaning’. CDN choice is part of week one.

If you’re thinking whether to keep Cloudflare or move to a Russian CDN, or need point expertise on infrastructure - write to me in Telegram @dimik90. On services:

Related: OPcache on shared hosting, CLS 0.377 → 0.002 in a day, form anti-spam without captcha.

Frequently asked questions

Does Cloudflare work in Russia or not?
It works, but unstably for a Russian audience. Since 2024 Russian ISPs have been blocking parts of the Cloudflare IP range via DPI - that shows up as slow loading or SSL handshake failures. The user doesn't understand this, they just close the site. If your audience is global and Russia is 5% - tolerable. If it's local Russian B2B - you lose a meaningful share of traffic. For global SaaS and content sites Cloudflare still makes sense.
Is Cloudflare about CDN or something more?
Originally about CDN (serving static from edge nodes). It grew into a wide stack: L7 DDoS protection, WAF (web application firewall), DNS hosting, Workers (serverless edge compute), Stream (video), R2 (S3-compatible storage). Most sites use only CDN and DNS - the other features are rarely needed by a small commercial site.
Are Yandex Cloud CDN and Selectel CDN alternatives?
Yes. Yandex Cloud CDN - a production service, servers in Moscow/St. Petersburg/Novosibirsk/Vladivostok, from 0.7 RUB per 1 GB outbound. Selectel - similar. Beget CDN is built into Beget hosting, free with an existing hosting plan, servers in Russia. All three solve static delivery for a Russian audience without regulatory risk. If you already host with Beget or Yandex Cloud - take CDN from them; otherwise pay separately.
What do I lose by giving up Cloudflare?
A handful of features that turned out unnecessary in my case. L7 DDoS protection - I have a small B2B site, no risk. Cloudflare Workers - needed for serverless edge compute, everything renders on shared PHP for me. Anti-bot mode - covered by six filters on the server-side form (see separate article). Extended analytics - I have Yandex Metrica. Cloudflare gives you 'everything in one place', but for small B2B most of it is overkill.
What if the client already has Cloudflare?
Three scenarios. First - if the audience is global and Russia is minor, leave it as is. Second - if the main audience is in Russia, switch to a Russian CDN: change NS at the registrar, in 24-48 hours DNS will update. Old zone ran on CF, new one runs on the host. Third - hybrid: static via Russian CDN, dynamic directly via hosting. More complex but works for large sites with traffic spikes.