Does StackPath Work in China? A Discontinued CDN, ICP & PIPL
StackPath has wound down its CDN and edge services — its site is now a blank placeholder and its WAAP product moved to another vendor — so a China-facing site on it must migrate regardless. The ICP filing and PIPL cross-border questions never sat with the CDN; they follow your site to wherever it moves next. A compliance-first look.
Does StackPath work in China?
There is no StackPath left to run on. It retired its CDN and wound down its edge services, so a China-facing site built on it has to migrate regardless — and the ICP and PIPL questions that remain belong to the site you move to, not to the delivery network.
StackPath's own site now loads as a blank placeholder, and its application-security product moved on: on March 6, 2024 Gcore "announced the acquisition of StackPath's web application and API protection (WAAP) solution," the security half carved off after the CDN itself was retired. Because StackPath was a delivery layer in front of your origin — not the host that gets filed, not your data store of record — it never carried an ICP filing of its own; that duty, under State Council Order No. 292 and MIIT Order No. 33, sits on the public site your visitors reach. Serve China from an offshore edge or origin and your users' personal data crosses the border — a transfer PIPL governs. The table below is what the live record shows and the rule each gap triggers.
This is a risk map, not a verdict — whether your migration triggers an ICP filing, in-country storage, a PIPL transfer mechanism, or all three turns on what you serve, your data and who your users are. Our China team can map your exposure with you →
What StackPath's own documentation says about China
| Fact | Primary source |
|---|---|
| StackPath's platform has been wound down — migration is the first fact, not the China question. StackPath's own site now serves only a blank placeholder page, and its documentation, support and status subdomains no longer resolve. On March 6, 2024 Gcore "announced the acquisition of StackPath's web application and API protection (WAAP) solution" — the security product carved off after the CDN itself was retired. Whatever you conclude about ICP or PIPL, a China-facing site on StackPath has to move to another delivery stack regardless. | Gcore press release (gcore.com), March 6, 2024; StackPath (stackpath.com), retrieved 2026-10-07 |
| A CDN sits in front of your origin, so it never carried an ICP of its own. StackPath delivered content; it was not the host that gets filed, and it held no personal-data store of record. The ICP filing (ICP 备案) a public mainland site needs — under State Council Order No. 292 and MIIT Order No. 33 — attaches to the hosting resource behind the edge, not to the delivery network. A foreign CDN like StackPath gave that site no mainland footing to file against, and a CDN serving mainland visitors presumes the site is already ICP-filed. | China's ICP regime — State Council Order No. 292; MIIT Order No. 33 |
| Serving China from an offshore edge or origin makes your users' data a cross-border transfer. StackPath ran no ICP-filed mainland delivery, so a China-facing site on it reached users from offshore. Personal information of Chinese visitors handled outside the mainland is a cross-border transfer under PIPL (notice, separate consent and a transfer mechanism, Articles 38–43); for a critical information infrastructure operator or large-volume handler, that data must stay in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). | PIPL Articles 38–43 and Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| The move off StackPath is where the compliance questions actually land. The only open choice is where your delivery and data live next — and whether that destination can be lawfully operated from the mainland. A public site reaching China still needs an ICP filing bound to in-country hosting, and any China personal data it stores still has to clear PIPL's cross-border rules or sit inside the mainland. Reachability was never the hard part; the licensing of where your site and its data live is. | State Council Order No. 292; MIIT Order No. 33; PIPL Articles 38–43 & 40 — 21YunBox compliance analysis, retrieved 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the StackPath question has a blunt answer before the compliance one: there is no StackPath left to run on. The company retired its content delivery network and wound down its edge services, its own site now loads as a blank placeholder, and its application-security product has moved to another vendor. So a China-facing site built on StackPath faces a migration no matter what you decide about licensing — and the questions that then matter, an ICP filing for the public site and where your users’ data is allowed to live, were never StackPath’s to answer in the first place. Reachability was always the easy half; the licensing of your site’s home is the part that follows you.
StackPath in China at a glance
| What decides it | Where StackPath stands now |
|---|---|
| Is it still available? | No. StackPath retired its CDN and wound down its edge services; its own site serves only a blank placeholder, and its documentation, support and status subdomains no longer resolve. Its WAAP security product was acquired by Gcore in March 2024. A China-facing site on StackPath has to migrate regardless. |
| What it was | A content delivery network and edge platform — a delivery layer in front of your origin, not the host that gets ICP-filed and not a store of record for your data. |
| Where ICP sits | On the public site behind the edge, under State Council Order No. 292 and MIIT Order No. 33 — never on the CDN. A foreign network with no mainland presence gave that site no in-country footing to file against. |
| Your China users' data | Handled through an offshore edge — a cross-border transfer of personal information PIPL governs. For a CIIO or large-volume handler, personal data collected in China must stay in the mainland, which no offshore edge or origin can do. |
| What reachability settles | Nothing that matters here. The hard part was never whether StackPath loaded; it is that StackPath is gone, and the licensing of where your site and data live follows you to the next stack. |
A platform that is gone — migration comes first
Before any China-specific question, there is a plainer one: is StackPath still somewhere you can deploy? Its own record says no. StackPath exited the content-delivery business and wound down its edge services; its website now serves only an empty placeholder page, and the documentation, support and status subdomains customers once relied on no longer resolve. The clearest live first-party marker of the wind-down is the acquirer’s own announcement — on March 6, 2024 Gcore said it had “announced the acquisition of StackPath’s web application and API protection (WAAP) solution,” the security half carved off after the CDN itself was retired. Whatever you concluded about ICP or PIPL, an application fronted by StackPath now has to move to another delivery stack. That makes migration the first fact of this page, not a footnote to it: the only open choice is where your delivery and data live next, and whether that destination is one you can lawfully operate from inside the mainland.
Where ICP sits — on the site behind the edge, not the CDN
It is tempting to ask whether StackPath itself was ever “ICP-filed.” It was not, and that is the wrong place to look. A content delivery network sits in front of your origin to move bytes; it is not the host a filing attaches to, and it holds no store of record for your data. An ICP filing (ICP 备案, under State Council Order No. 292 and MIIT Order No. 33) binds to the public-facing site your visitors reach from inside China, hosted on a mainland resource — and a CDN delivering to mainland users presumes that site is already filed. StackPath, a foreign network with no ICP-filed presence inside the mainland, gave the site in front of it no in-country footing to anchor a filing to. So the ICP obligation never belonged to StackPath; it belonged to your site, and it follows that site to whatever you move it onto next.
Your China users’ data and the border
The same logic decides the data question. A site served to China through StackPath’s offshore edge handled its visitors’ personal information — request data, and everything the origin behind it collects — outside the mainland. Under China’s Personal Information Protection Law that is a cross-border transfer, and the handler — you, not the delivery network — has to give notice, obtain separate consent, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. If you are a critical information infrastructure operator or a large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a residency duty no offshore edge or origin can meet. Moving off StackPath is the moment to settle where that data will actually live.
This is a risk map, not a verdict: whether your move off StackPath triggers an ICP filing, in-country storage, a PIPL transfer mechanism, or all three depends on what you serve, how much personal data you hold, and who your users are — worth putting to counsel before you rebuild.
Where 21YunBox fits — a compliant overlay, not a migration
StackPath is gone, so a migration is already on your plan — but the hard part of a China launch was never swapping one delivery layer for another. It is being cleared to serve the mainland at all: an ICP-filed origin inside China and a lawful home for your users’ data. That is the piece we add. Whatever stack your site lands on next, 21YunBox places compliant, ICP-filed delivery from inside the mainland in front of your existing origin — no rebuild, no second codebase, and no re-architecting onto a China-only platform. Our China team maps your ICP and PIPL cross-border obligations against your entity, your data volumes and your users, then stands up the in-country delivery and storage a lawful China presence requires, while the application you choose keeps running where you run it.
Related reading:
