CDN Latency: East vs West Benchmark 2026
Enterno.io measured TTFB for the top-5 CDN providers (Cloudflare, AWS CloudFront, Fastly, Google Cloud CDN, Yandex Cloud CDN) from 4 geographies (Moscow, Frankfurt, Virginia, Singapore) in March 2026. Cloudflare wins globally (median 42ms), but within Russia Yandex Cloud CDN leads (38ms vs 31ms). Fastly is the consistency leader (low p99). AWS CloudFront is the most uneven (SEA great, RU average).
Below: key findings, platform breakdown, implications, methodology, FAQ.
Key Findings
| Metric | Pass/Value | Median | p75 |
|---|---|---|---|
| Global median TTFB (all CDNs) | 58ms | 58 | 110 |
| Cloudflare median (global) | 42ms | 42 | 85 |
| Fastly median | 52ms | 52 | 92 |
| AWS CloudFront median | 68ms | 68 | 125 |
| Yandex Cloud CDN median (RU) | 31ms | 31 | 54 |
| Cloudflare from Moscow | 38ms | — | — |
| AWS CloudFront from Moscow | 92ms | — | — |
| Cloudflare from Singapore | 22ms (best) | — | — |
Breakdown by Platform
| Platform | Share | Detail | — |
|---|---|---|---|
| Cloudflare (global) | 21% | median: 42ms | — |
| AWS CloudFront | 14% | median: 68ms | — |
| Fastly | 4% | median: 52ms | — |
| Google Cloud CDN | 5% | median: 58ms | — |
| Yandex Cloud CDN | 2% (global), 24% (RU) | RU median: 31ms | — |
| Azure Front Door | 3% | median: 74ms | — |
Why It Matters
- For RU audience: Yandex Cloud CDN >> Cloudflare (31ms vs 38ms). But Yandex only in Moscow/SPB/Yekaterinburg
- For global (US/EU/APAC) — Cloudflare remains the leader. Fastly consistent on p99 (less tail latency)
- AWS CloudFront via Frankfurt edge in RU — high latency ~100ms. Avoid if your primary audience is Russian
- Multi-CDN (Cloudflare + Yandex) solves it: global users → CF, RU users → Yandex. Via DNS-based routing
- Latency 40ms vs 80ms on CDN = CWV LCP 50-100ms difference. Don't ignore
Methodology
Enterno.io probes from 4 regions (msk/fra/iad/sin) × 5 repeats × every 10 min × 30 days. Target: static file (1 KB) on test site behind each CDN. Median/p75/p99 computed from 300k data points.
Why teams trust us
How it works
Enter IP or domain
Detect geolocation
Get ISP and ASN info
Why check IP Geolocation?
IP geolocation identifies the location of a server, user, or traffic source. Essential for CDN configuration, GeoIP rules, and security anomaly analysis.
Accurate Geolocation
Country, region, city, postal code, and timezone by IP.
ASN / ISP Data
Provider, autonomous system name, and network range.
Proxy Detector
VPN, proxy, Tor, and hosting flags — protection against fraud and bots.
Search History
Save checks and compare IP geolocation across multiple lookups.
Who uses this
DevOps
server IP check
Security
threat origin ID
SEO
CDN node check
Developers
geo-block debugging
Common Mistakes
Best Practices
Get more with a free account
IP check history, API access and geolocation change monitoring.
Sign up freeLearn more
Frequently Asked Questions
Multi-CDN — overkill for small sites?
Yes. If < 100k visitors/mo — one CDN is enough. Multi-CDN setup complexity isn't justified.
Is Yandex Cloud CDN reachable outside Russia?
Yes, but edge nodes are only in Russia. International users get latency through Russia backbone (not optimal).
CDN vs origin — which is faster?
CDN is always faster on cache hit. First request (cache miss) ≈ origin. Second+ — always faster on CDN.
How to measure my CDN latency?
<a href="/en/check">Enterno HTTP checker</a> measures TTFB from RU+EU+US in one click. Or <a href="/en/ping">ping</a> for network layer.