CDN and edge platform · Snapshot 23 October 2026
Sites on Google edge
906 measured sites rely on Google edge as their cdn and edge platform. How common it is by popularity band, how its customers configure related checks, and the continuity steps worth taking.
- Sites
- 906
- Median readiness index
- 68/100
- Profiles
- 567
2.3% of all measured sites
all sites: 64
top-50K sites
Share by popularity band
| Chrome UX Report band | Share of measured sites | Sites |
|---|---|---|
| Top 1K | 4.4% | 21 |
| Top 5K | 3.3% | 71 |
| Top 10K | 3.4% | 87 |
| Top 50K | 2.4% | 453 |
| Top 100K | 2.1% | 109 |
| Top 500K | 1.5% | 81 |
| Top 1M | 1.5% | 84 |
Related checks among Google edge customers
| Check | Lane | Observed | All sites | Measured |
|---|---|---|---|---|
| HTTP/2 negotiated | Accelerate | 98% | 90% | 903 |
| HTTP/3 advertised | Accelerate | 73% | 37% | 884 |
| HTML compressed | Accelerate | 93% | 93% | 881 |
| Static files cached for 30 days or more | Accelerate | 54% | 51% | 673 |
| HSTS kept for at least a year | Harden | 38% | 34% | 884 |
| TLS 1.3 negotiated | Harden | 97% | 91% | 903 |
| Modern image formats in use | Accelerate | 43% | 40% | 743 |
Continuity steps for Google edge customers
- Document how the site would be served if the edge layer misbehaves: which DNS records change to bypass the proxy, what that exposes, and who can make the change.
- Keep the origin's own TLS certificate valid so that a bypass does not break HTTPS.
- Keep edge configuration (redirects, headers, cache and firewall rules) exported or in version control so it can be rebuilt or moved.
- Rehearse serving from the origin during a quiet period, so you know it can carry traffic without the cache.
Status Is UP dependency continuity toolkitWebsite recovery planService guide: Google Cloud