MaxCDN and SecureCDN are Retiring; Here's What It Means for You (2024)

Take A Short Walk With Me Through StackPath History

In 2016, MaxCDN (the company) became a part of StackPath, and MaxCDN (the service) was the underpinnings for SecureCDN, the first StackPath-branded service, released the same year. In 2017, Highwinds (the company) joined the family, and in 2018 we merged the capabilities and legacies of MaxCDN/SecureCDN into Highwinds CDN to create StackPath CDN. We stopped selling MaxCDN and SecureCDN to new customers at that time but never stopped supporting both products or their fanatically loyal customers.

We’ve decided the time has come to retire the MaxCDN and SecureCDN products—they’ve earned a nice retirement! That way we can focus more attention on taking StackPath CDN even farther, and make sure all of our customers have the advantages of integration with StackPath Edge Computing and Edge Security offerings.

If you’re a MaxCDN or SecureCDN user, don’t worry: it’s not happening overnight. We’re dedicated to making the transition as smooth as possible. That’s why I’d like to share some details now, giving you plenty of lead time to plan, test, and perform your migration. And in addition to this article, we have documentation and people to help you every step of the way.

The Details

• On August 26, 2022, technical support will no longer be available for:
  • MaxCDN service accessed via cp.maxcdn.com
  • MaxCDN portal accessed via cp.maxcdn.com
  • SecureCDN service accessed via app.stackpath.com
  • SecureCDN portal accessed via app.stackpath.com
• On December 31, 2022, the services and portals above will no longer be in operation.

Here’re Some Answers to Questions We Know You May Have:

Q. Does this announcement impact me?
A: If you use app.stackpath.com (for Secure CDN) or cp.maxcdn.com (for MaxCDN), you will be impacted and should plan to migrate your account. If you use control.stackpath.com you are not impacted by this change.

Q: What exactly will happen on August 26?
A: On August 26, 2022, at 23:59 UTC, support for MaxCDN and SecureCDN officially end, and you will no longer be able to open a ticket or contact customer service to report or get help with service, performance, security, or other account issues.

Q: What exactly will happen on December 31?
A: No later than December 30th, 2022, at 23:59 UTC, the MaxCDN and SecureCDN services and their respective customer portals will shut down permanently. At that time no data, configurations, or account information will be accessible, stored, or maintained.

Q: Can migration to StackPath CDN be automated?
Can account information, users, zones/sites, configurations, and SSL certificates move automatically?
A: Unfortunately, no. Though SecureCDN, MaxCDN, and StackPath CDN have the same or equivalent capabilities and have run within the same overall operational infrastructure, for continuity we have kept them as separate platforms. This limits our options for automating the process. However, most SecureCDN and MaxCDN accounts have one user and one CDN zone/site, making manual migration straightforward. We’re sorry for the inconvenience this causes, but we are committed to providing ample documentation and simplifying the process as much as possible.

Q: How do I migrate from SecureCDN or MaxCDN to StackPath CDN?
A: Manually migrating to StackPath CDN is relatively straightforward:

1. Create (or log into) an account at control.stackpath.com
   1. Get Started with StackPath
2. Select a StackPath CDN stack
3. Configure a CDN site on your new StackPath CDN stack
   1. Create and configure a StackPath CDN site
   2. Create and Manage SSL Certificates
4. Log in to the customer portal for your legacy product
   1. app.stackpath.com for Secure CDN
   2. cp.maxcdn.com for MaxCDN
5. Disable your legacy zone/site and cancel your legacy subscription
   1. How to cancel MaxCDN
   2. How to cancel SecureCDN

Q: What else do I need to know about migrating from MaxCDN or SecureCDN to StackPath CDN?
A: Site configurations are not live in production until the appropriate DNS changes have been made to direct traffic to your new StackPath CDN site(s). After those changes are made, the new DNS records will need to propagate the StackPath CDN. It is important not to delete any legacy MaxCDN or SecureCDN zone/site and account until AFTER the new DNS records are fully propagated.

Q: What if I have trouble setting up StackPath CDN?
A: If you have any trouble setting up your StackPath account or your StackPath CDN site, please contact StackPath Support via email, or through chat or ticket in the customer portal.

Q: What if I have product or price questions?
What if StackPath CDN is missing features or functionality I need?
A: StackPath Sales is available to answer questions about product capabilities, prices, and solutions strategies via , chat on our website, or +1 (877) 629-2361.

Q: Are there any steps I need to take if I’m also a StackPath WAF customer?
A: StackPath WAF is the WAF built into SecureCDN. It has not been available with MaxCDN. If you have used WAF with SecureCDN and continue to want WAF protection, add WAF to your new stack in control.stackpath.com, and configure a WAF site with the same settings as you have used in SecureCDN.

Q: Where can I find more information about StackPath products and features?
A: Please visit our website if you’d like to learn more before migrating your account and services. StackPath Sales is available to answer questions about product capabilities, prices, and solutions strategies via email, chat on our website, or +1 (877) 629-2361.

Again, we’re very sorry for the inconvenience this causes. We’re excited to get all our CDN customers using the same product and the additional capabilities and future opportunities it will bring you. We’ll continue communicating to MaxCDN and SecureCDN customers throughout the process for the rest of this year, sharing as much detailed information as possible.

Thanks for being StackPath customers and journeying with us for so long.