Website · Documentation · Pricing
Overview
NAVER Cloud Platform Global CDN delivers files and media through a partner network in Classic and VPC environments. Global CDN retires on December 31, 2026, and new creation is blocked. Existing users must migrate to Global Edge, NAVER’s replacement CDN.
NAVER’s September 17, 2026 release added console migration to Global Edge. Plan and test the migration before the retirement date. The Global CDN capabilities described here do not establish identical behavior or pricing on Global Edge.
Network
Features
| Feature | Supported |
|---|---|
| Web application firewall | Not listed |
| Bot protection | Not listed |
| DDoS protection | Not listed |
| Rate limiting | Not listed |
| HTTP/3 (QUIC) | Not listed |
| TLS 1.3 | Not listed |
| Tiered caching | Not listed |
| Origin shield | Not listed |
| Instant cache purge | ◐ Partial |
| Serve stale while refreshing | Not listed |
| Serve stale on origin errors | Not listed |
| Image optimization | Not listed |
| On-demand video | ✓ Supported |
| Live video | Not listed |
| Digital rights management | Not listed |
| HLS / DASH packaging | Not listed |
| WebSockets | Not listed |
| Signed URLs | ✓ Supported |
| Edge compute | Not listed |
| Edge functions | Not listed |
| Key-value storage | Not listed |
| Configuration API | ✓ Supported |
| Real-time logs | Not listed |
| Log export | Not listed |
| Terraform provider | Not listed |
✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.
- Origins: web servers or NAVER Object Storage, using HTTP or HTTPS.
- Delivery: HTTP/2, cache controls and cache purge.
- Access and monitoring: token/referrer rules, usage reports and access logs.
Pricing
Developer tools
Use the console’s Global Edge migration feature for an existing Global CDN service. It was added in NAVER’s September 17, 2026 release. Complete the migration before Global CDN retires on December 31, 2026.
Validate origins, domains, certificates, cache rules, token/referrer controls, purge behavior and logs on the replacement. Check the applicable Classic or VPC setup and update application or DNS references as needed. The Global CDN guide and API reference describe the retiring product; verify Global Edge’s own configuration and API requirements.
When it fits
- Existing Global CDN customers planning their move to Global Edge before December 31, 2026.
- NAVER Cloud workloads evaluating Global Edge as the replacement delivery service.
Before you choose
- New Global CDN deployments: new creation is blocked.
- Workloads relying on Global CDN after December 31, 2026.
- Migrations that assume Global Edge has identical configuration, coverage or pricing without checking its own documentation.
Sources
- www.ncloud.com/product/contentDelivery/globalCdn
- guide.ncloud-docs.com/docs/en/globalcdn-overview
- www.ncloud.com/charge/calc/ko?category=contentDelivery#globalCdn
- www.ncloud.com/support/notice/all/2241
- guide.ncloud-docs.com/release-20260917/docs/en/releasenote-20260917
- aws.amazon.com/s3/pricing/
- cloud.google.com/storage/pricing
