Reach viewers wherever they are and provide them with a fast and reliable experience
Deliver content fast to a global audience by bringing content from the server closest to your users. If an origin server fails, the next nearest server serves as a backup to ensure uninterrupted delivery and high availability. When traffic spikes, a highly distributed network of cache servers protects the origin server and handles large amounts of traffic.
You can create and configure your CDN from the web console. The settings are applied immediately to servers worldwide, allowing you to deliver your content with speed and consistency. You can also cache data, compress files, and configure more options to suit your needs.
You can pull content from any origin server over HTTP or HTTPS. You can set NAVER Cloud's Object Storage and Server as origins, and specify any port for connections.
Leverage our network of cache servers to handle large amounts of traffic at lower costs. Global CDN offers pay-as-you-go pricing based on data transfer and number of requests, making it easier for you to manage costs.
You can configure various caching options that best suit your needs from the NAVER Cloud Platform console. You can set values for cache expiration duration and time to live (TTL) for different content and extensions using origin cache-control headers.
Global CDN supports existing standard web protocols like HTTP/1.0 and HTTP/1.1, plus HTTP/2, which was standardized by the IETF in 2015.
Global CDN supports content integration with multiple origin servers through protocols, such as HTTP, HTTPS, and HTTP/2.
You can set various existing web servers and NAVER Cloud's Object Storage and Servers as orgin servers, and you can also specify a port for CDN to connect to the server.※ If you set to use the HTTPS protocol, the cache must communicate with origin servers through the HTTPS protocol. If you use your own web server as an origin server, your server must run in a public network for external communication.
You can use both HTTP and HTTPS or only allow HTTPS. Choosing HTTPS protocol enhances security for all content delivery paths by allowing HTTPS communication with the origin server. NAVER Cloud's Global CDN offers access permission based on referrer domains and will allow the creation of a secure URL based on secure tokens.
Cache purging is a key feature that ensure the reliability in content delivery. When the content in the origin server is changed, Global CDN quickly purges content and immediately reflect the changes to caching servers across the world. You can purge the content stored on hundreds of thousands of caching servers across the world in a matter of seconds. When the original content chanages, the existing cache is deleted to synchronize with the original server upon user request.
CDN+ provides logs for requests to access your content to help you analyze usage. These logs are automatically stored in Object Storage on a regular basis.
Click [Diagnose] to assess the quality of CDN+ on your own. Contact us if you want advice on the test results.
Classification | Billing Units | Usage section | Pay-as-you-go |
|---|---|---|---|
Monthly transmission fee | GB | 200GB or less | - |
Monthly transmission fee | GB | More than 200GB - 10TB or less | - |
Monthly transmission fee | GB | More than 10TB - 50TB or less | - |
Monthly transmission fee | GB | More than 50TB - 150TB or less | - |
Monthly transmission fee | GB | More than 150TB - 500TB or less | - |
Monthly transmission fee | GB | More than 500TB | - |
(VAT Excluded)
Classification | Billing Units | Usage section | Pay-as-you-go |
|---|---|---|---|
Monthly request fee | 10,000 cases | Same for all sections | - |
(VAT Excluded)
Service fee = Monthly transfer fee + Monthly request fee
Monthly transfer fee = Sum of total CDN transfer amount fees for the month
Monthly request fee = The number of total CDN requests for the month
Guide to data collection for monthly service charges
The sum of monthly transmission fee and monthly request fee from [the last day of the month before previous month – 3 days] to [the last day of the previous month – 4 days]
[Example] May service charges breakdown = the sum of transmission fee and the request fee from March 28 to April 26