Overview
Google Cloud CDN is Google’s content delivery service for web applications, APIs, downloads, and other cacheable HTTP content. It runs behind a global external Application Load Balancer and can use Google Cloud backends, Cloud Storage, or an external HTTP origin. Media CDN is a separate Google Cloud product for large-scale video and media delivery.
Network & Architecture
Cloud CDN serves content through Google’s global edge network and uses an external Application Load Balancer as its request-routing layer. Google documents more than 200 network edge locations, but that list covers access to multiple Google Cloud services and should not be interpreted as a Cloud CDN cache count. Origins can run in Google Cloud or outside it through an internet network endpoint group.
Features
| Feature | Supported |
|---|---|
waf | ✓ |
ddos | ✓ |
http3_quic | ✓ |
tls13 | ✓ |
instant_purge | ✓ |
stale_while_revalidate | ✓ |
signed_urls | ✓ |
api_first | ✓ |
realtime_logs | ✓ |
Legend: ✓ = Supported, Partial = Partially supported, ✗ = Not supported
Pricing
Cloud CDN uses usage-based pricing. The bill can include cache data transfer out, cache fill, HTTP or HTTPS cache lookup requests, and load-balancing or origin-related charges on misses and non-cacheable traffic. Rates vary by destination and volume. The dated Google Cloud pricing page is the source of truth for a cost estimate.
Integrations & DevEx
Cloud CDN is configured on backend services or backend buckets attached to an external Application Load Balancer. Supported origin patterns include Compute Engine, Cloud Storage, Cloud Run, Google Kubernetes Engine, third-party object storage, and external HTTP backends. Requests are available in Cloud Logging, with metrics exposed through Google Cloud monitoring services.
When it fits
- Applications already using Google Cloud load balancing or Google Cloud origins.
- Teams that need an HTTP CDN with configurable cache policy, signed requests, and Cloud Logging.
- Workloads that need to place a Google-managed edge in front of an external HTTP origin.
When it doesn’t
- Teams looking for a standalone CDN that does not depend on Google Cloud load-balancing configuration.
- Large-scale live or on-demand media workloads that belong on Google’s separate Media CDN product.
- Buyers who need a single flat delivery rate independent of destination, request volume, cache fill, and origin architecture.