Company snapshot
| Category | Google Cloud CDN | MaxCDN |
|---|---|---|
| Status | active | defunct |
| Founded | — | — |
| Headquarters | — | — |
| Website | — | — |
| Docs | — | — |
Overview
Google Cloud CDN is a content delivery network integrated with Google Cloud. It sits behind Google Cloud Load Balancing to cache and serve HTTP(S) content from edge locations. Typical users are teams already running workloads on Google Cloud that want CDN caching, signed URLs, modern TLS, and consistent operations across the platform. The service emphasizes policy-driven caching, fast invalidation, and security integration through Cloud Armor. Pricing follows a pay-as-you-go model that varies by region and usage.
MaxCDN was a content delivery network (CDN) provider founded in 2009, focused on accelerating static and dynamic content for websites and applications. It served small to large businesses with a global network of edge servers. Acquired by StackPath in 2016, MaxCDN was retired in 2022, and StackPath itself shut down all services in 2024. The service is now defunct, with no active operations or support.
Network & Architecture
Google Cloud CDN uses Google’s global edge and backbone to terminate HTTP(S) traffic close to end users and fetch from origins over Google’s private network. Coverage spans major regions in North America, Europe, and Asia-Pacific, with additional presence in other geographies. Strengths include integration with Google Cloud Load Balancing, Anycast routing, and private backbone connectivity from edge to origin. Limitations can include fewer CDN-specific knobs than specialist CDNs and feature gaps for advanced video packaging.
—
Feature comparison
| Feature | Google Cloud CDN | MaxCDN |
|---|---|---|
waf | ✓ | ✗ |
bot_mitigation | ✓ | ✗ |
ddos | ✓ | ✗ |
rate_limit | ✓ | ✗ |
http3_quic | ✓ | ✗ |
tls13 | ✓ | ✗ |
tiered_cache | ✓ | ✗ |
origin_shield | ✓ | ✗ |
instant_purge | ✓ | ✓ |
stale_while_revalidate | ✓ | ✗ |
stale_if_error | ✓ | ✗ |
image_optimization | ✗ | ✗ |
video_vod | ✗ | ✗ |
video_live | ✗ | ✗ |
drm | ✗ | ✗ |
hls_dash_packaging | ✗ | ✗ |
websockets | ✗ | ✗ |
signed_urls | ✓ | ✗ |
edge_compute | ✗ | ✗ |
functions | ✗ | ✗ |
kv_storage | ✗ | ✗ |
api_first | ✓ | ✓ |
realtime_logs | ✓ | ✓ |
log_push | ✓ | ✗ |
terraform | ✓ | ✗ |
Legend: ✓ = Supported, ✗ = Not supported, — = Not listed
Pricing
Pay-as-you-go pricing with regional rates for cache egress and request charges. Total cost depends on geography, volume, and cache behavior. See cloud.google.com/cdn/pricing for current details.
—
Integrations & DevEx
Deep integrations include Google Cloud Load Balancing for traffic ingress, Cloud Armor for WAF and DDoS protections, Cloud Storage and Compute Engine for origins, and Cloud Logging and Monitoring for observability. Infrastructure as code is supported via Terraform, and a REST API enables CI/CD automation.
—
When it fits
- Workloads already hosted on Google Cloud that need an integrated CDN layer.
- Teams standardizing on Cloud Load Balancing, Cloud Armor, and Cloud Logging.
- Organizations that want signed URLs, HTTP/3, fast purge, and policy-driven caching.
- Buyers who prefer Terraform and API-first management across cloud services.
—
When it doesn’t
- Multi-cloud environments seeking provider-neutral or MultiCDN routing.
- Advanced video workflows needing packaging, DRM, or low-lency live features.
- Use cases requiring built-in image optimization pipelines.
- Projects that rely on WebSocket-heavy bidirectional traffic at the edge.
—
History & Notes
—
MaxCDN was known for its developer-friendly API and real-time purge capabilities, serving a wide range of clients until its integration into StackPath. The acquisition aimed to combine MaxCDN’s CDN expertise with StackPath’s security and edge computing, but integration challenges and rising costs led to customer dissatisfaction. The sudden shutdown of StackPath in 2024, with no support or leniency, left customers scrambling. No official MaxCDN website or documentation remains active.