Historical provider.
Current availability of the listed service is not confirmed. Acquired by StackPath in 2016-07.

Documentation

Overview

MaxCDN was a Los Angeles-based CDN founded in 2009. It provided HTTP caching and content delivery, with API tools for managing delivery zones and reports.

StackPath ’s July 2016 launch announcement identified MaxCDN as an acquired business incorporated into its platform. This profile covers the historical brand, rather than a current independent subscription.

Network

MaxCDN distributed cached HTTP content across its delivery infrastructure.

Current MaxCDN cache-city locations are unconfirmed. For replacement coverage, check the current delivery provider’s locations.

Past features

Historical controls

  • Pull-zone creation and configuration through an API.
  • File-specific and whole-zone cache purges.
  • Usage reporting through official client libraries.

The archived documentation includes authentication, raw logs, origin shielding and SSL. Use the tools to recover legacy settings, then test equivalent cache behavior and purge timing on the replacement.

Service status

MaxCDN became part of StackPath . Akamai later bought selected StackPath enterprise contracts. Check your account notices to find the provider handling your old deployment.

Export origins, hostnames, certificates, cache rules and access controls before configuring another CDN. Test the settings and price the replacement using your current traffic.

History timeline

  • 2009 — MaxCDN founded — Its historical company profile lists Los Angeles headquarters.
  • 2016-07-25 — StackPath launch identified MaxCDN acquisition — MaxCDN had already been acquired; precise closing day not established by this release.
  • 2022-12-19 — Meteor published legacy MaxCDN migration notice — The notice asked customers to update its CDN hostnames ahead of a December31deadline.
  • 2023-08-24 — Akamai acquired selected StackPath contracts — Not every MaxCDN account or network asset was included.

Budgeting for a replacement

No current independent MaxCDN tariff is modeled. Use current delivery and operation rates for a replacement estimate.

Estimate a migrated workload using the current provider’s quote, including traffic, requests, minimum commitments and any storage or security charges.

Historical integrations

Official API documentation and the Node.js client remain available on GitHub. They document historical authentication, zones, reports and purge requests.

Use these references to understand an old deployment; validate current endpoints, credentials and supported settings with the contracted successor before reuse.

What to know

  • Understanding legacy MaxCDN API calls, pull zones and invoices.
  • Planning replacement of old CDN hostnames and cache configurations.

Planning a replacement

For a new deployment, use a current provider. For an old MaxCDN integration, confirm the active hostnames and account support before reusing credentials, API tools or cache rules.

History

Acquisition

By StackPath ’s July 25, 2016 launch announcement, MaxCDN had been acquired and incorporated into its platform.

Legacy-service transition

Meteor’s December 2022 customer notice describes replacing its MaxCDN hostnames ahead of an announced December 31 deadline. Use the notice to trace that migration; check the account’s active hostnames and current provider before making further changes.

Akamai subsequently acquired selected StackPath enterprise customer contracts in August 2023 after StackPath’s decision to leave the CDN business. Personnel and technology were excluded; every former MaxCDN account is not assumed to have transferred.

Sources