Akamai Has Left China: What Happened on 30 June 2026 and What to Do Now
Akamai decommissioned its mainland China CDN on 30 June 2026. If your China traffic still routes through it, it is now being served from outside the country. What changed, and the options that remain.
Does Akamai work in China?
Akamai decommissioned its mainland-China CDN on 30 June 2026. That date has passed. If your China traffic still routes through Akamai, it is reachable and reasonably fast from mainland China. The remaining risk sits in whatever else the page requests. Measured fact: from a probe inside mainland China (Alibaba Cloudcn-zhangjiakou), three runs, 2026-08-27, akamai.com loaded in a median 0.4 seconds (largest-contentful-paint 0.5s), completing all three runs — consistent with a vendor that already operates delivery infrastructure inside China. Need an Akamai China Boost? Get a Free Site Audit.
Our fully managed overlay adds China speed and compliance to your existing Akamai setup—no rebuilds, no extra DevOps.
Get In TouchLet us handle China so you can focus on growth.
What Akamai's own documentation says about China
| Fact | Primary source |
|---|---|
| Akamai notified customers in January 2025 that its China CDN services would reach decommission on 30 June 2026, after which remaining requests are served from neighbouring countries unless a country-specific partner solution is activated. | South China Morning Post — Akamai to cease CDN operations in China |
| Akamai cited a return to its core focus on global security and edge compute, together with the regulatory burden of maintaining in-country infrastructure, and moved to a partner model with Tencent Cloud and Wangsu rather than direct operations. | DataCenterDynamics — Akamai to end CDN services in China |
| Whoever serves the traffic afterwards inherits the regulatory gate: a site delivered from inside mainland China needs an ICP filing, and that filing is bound to the access provider — so changing provider means updating the filing, not just DNS. | Alibaba Cloud — ICP filing prerequisites |
| Delivery from inside mainland China — the only arrangement that removes the cross-border round trip — carries the regulatory gate with it: "ICP filing applies only to servers located in the Chinese mainland", and the filing binds to the access provider, not only the domain. | Alibaba Cloud — ICP filing prerequisites |
Sources verified by the 21YunBox China engineering team on 2026-08-28.
Akamai China: where things stand now
Status as of August 2026: the deadline has passed. Akamai decommissioned its mainland-China CDN on 30 June 2026.¹ If you have not migrated, your China traffic is no longer being served from inside the country — it is falling back to points of presence in neighbouring markets, outside the Great Firewall. This is not a future planning problem any more; it is a live one.
Quick‑Glance Timeline
| Milestone | Date | What It Means |
|---|---|---|
| Customer notice sent | 08 Jan 2025 | Akamai formally announces exit. |
| New mainland provisioning ends | 30 Sep 2025 | No new sites can be onboarded to Akamai China POPs. |
| Mainland POPs de‑commissioned | 30 Jun 2026 | All traffic falls back to HK/SG or further. |
Does Akamai Work in China Today?
Akamai’s global edge network stops at China’s digital border. Inside China it relies on third‑party partners rather than its own POPs, which means no self‑service portal and inconsistent performance.
- Average TTFB reported by customers: 550 ms – 1.2 s.
- Static assets often routed through Hong Kong, Singapore or Tokyo.
- Dynamic HTML can be throttled or reset by the Great Firewall (GFW), causing 5 s+ white‑screens or outright timeouts.
Why Is Akamai Leaving China?
In January 2025 Akamai notified customers that it will discontinue its China CDN, citing a return to its core focus on global security and edge compute and the high regulatory burden of maintaining in‑country infrastructure.²
What Happens After 30 June 2026?
- Latency jump: Traffic will fall back to Hong Kong nodes, adding 150–300 ms (often more during congestion).
- Operational burden: You’ll need new contracts and China regulatory paperwork if you move to local CDNs—unless you add an overlay that handles compliance for you.
Fully Managed Overlay — 21YunBox China Website Performance Optimizer
21YunBox Optimizer is a turnkey layer that snaps onto your current Akamai stack:
- No rebuild, no new pipeline – we deploy optimization fixes directly on Akamai nodes.
- Instant mainland POP coverage – traffic is automatically routed through 40+ in‑China acceleration hubs.
- Hands‑off China compliance – we take care of ICP, real‑name auth, logging, and all required filings.
- Self‑service controls optional – keep your Akamai workflows; use our dashboard only if you want deeper China‑specific rules.
How the Optimizer Fits Into Your Current Akamai Setup
- CNAME or DNS alias – point
cn.yoursite.comto our overlay; global traffic continues hitting Akamai as usual. - Edge optimization rules – we add compression, image/web‑font re‑formats, and protocol tweaks directly on Akamai nodes.
- Acceleration into China – optimized objects ride our private backbone into mainland POPs for sub‑100 ms TTFB.
- Compliance handled – you stay on your existing origin; we shoulder the China‑side regulations.
Performance Benchmarks
| Scenario | First‑Byte Time (TTFB) | Full Page Load |
|---|---|---|
| Akamai global POP → Beijing user | 550 ms – 1 s | 4–7 s |
| Akamai global POP → Shanghai user (peak) | 800 ms – 1.3 s | 6–10 s |
| 21YunBox Optimizer → any tier‑1 Chinese city | < 100 ms | 1.2–1.8 s |
Data from 50+ production sites, Q1 2025 synthetic RUM.
China compliance checklist
Good news: the Optimizer bundle covers each item below out of the box.
- ICP Filing (MIIT) – website licence unique to your domain.
- Real‑Name Authentication – verified Chinese phone & legal entity.
- PSB Police Filing – URL record with local Public Security Bureau.
- Log Retention & Cross‑Border Transfer Guardrails – 6‑month storage inside China, alarms on PII exports.
Migration checklist — if you have not moved yet
- Audit your current Akamai property rules and China traffic share.
- Decide whether to re‑platform, move to a domestic CDN, or overlay.
- Engage 21YunBox for a free latency & compliance gap report.
- Deploy the Optimizer via CNAME (average cut‑over < 2 hours).
- Validate performance with our built‑in synthetic & RUM dashboards.
Common Misconceptions
“I’ll just serve China from Hong Kong—close enough.” Hong Kong routes still cross the GFW; expect packet loss, throttling, and regulatory gaps.
“We can wait until 2026 to worry about this.” China ICP filings alone can take 4–6 weeks. Add migration & testing and you risk an outage.
“Local CDNs give me everything I need.” They deliver speed, but you still shoulder compliance, Chinese‑language contracts, and 24/7 bilingual support. The overlay offloads that.
Alternatives to Akamai China POPs
| Option | Pros | Cons |
|---|---|---|
| Move to a domestic CDN (Alibaba Cloud, ChinaCache, Wangsu) | Native POP density, government ties | Rebuild rules, dual dashboards, Chinese contracts, DevOps overhead |
| Hybrid: Keep Akamai + deploy 21YunBox Optimizer (recommended) | 2‑hour cut‑over, keep existing pipelines, compliance handled | Small additional CNAME hop |
| Full migration to another global CDN w/ China partner (Cloudflare, Edgio) | Familiar UI | Same mainland partner dependence; migration effort similar to domestic move |
Need help? Start a conversation with us—we’ll review your Akamai setup and show the gains you can expect.
Related Resources
¹ The Register & DataCenterDynamics, Jan 2025; ² Akamai customer notice, Jan 2025: https://content.akamai.com/index.php/email/emailWebview.
