Yandex Cloud CDN pricing policy

To estimate your service costs, see the pricing in this section.

All prices in RUB and KZT are inclusive of VAT; in USD, net of VAT.

The cost of using Cloud CDN is based on:

• Total CDN resources.

• Outgoing traffic over the 150 GB free monthly quota per resource, charged per 1 GB.

  Deleting a resource forfeits any remaining free traffic. You cannot transfer traffic from one resource to another.

  You pay for outgoing traffic from CDN servers, including traffic requested from user resources of Yandex Cloud services, e.g., Yandex Compute Cloud VM instances. Inbound traffic to the CDN servers from Yandex Cloud services and resources or from the internet is free of charge.

• Number of requests to CDN resources in excess of the 100,000,000 free monthly threshold, charged per 100,000 requests.

• Paid features enabled for your resources, such as origin shielding, log export, and dedicated IP addressing.

Traffic between the origin and CDN serversTraffic between the origin and CDN servers

Cloud CDN does not guarantee any particular percentage of cached requests hitting the cache (cache hits). If the CDN server cannot respond to a request from the cache, it accesses and gets content from the origin. Depending on your settings for caching, cache cleanup, new content publication, or the nature of user requests, the number of requests to the origin and the amount of data it sends back may increase. At the same time, the amount of data the origin sends to CDN servers may be comparable to the amount of outgoing CDN traffic.

Cloud CDN does not charge for incoming traffic CDN servers are getting from origins, even when the origin is outside of Yandex Cloud. Outgoing traffic from Yandex Cloud resources to CDN servers is treated as internal and Yandex Cloud services do not charge you for it. For example, if the origin is an Object Storage bucket, transferring data from the bucket to Cloud CDN is not billed on the Object Storage side.

At the same time, the origin's operating costs may depend on the number of incoming requests. For example, if requests are handled by a function, the number of its calls will be factored in. If there is a traffic filtering or DDoS protection service upstream of the origin, its costs may depend on the amount of processed traffic, bandwidth, or request count.

Make sure the origin can withstand potential peak loads, and its pricing conditions do not imply substantial extra costs. If required, protect the origin at the application layer (L7) of the OSI model, e.g., using Yandex Smart Web Security.

Yandex Cloud does not compensate for consequential losses due to increased load on the origin.

Prices for the Russia regionPrices for the Russia region

You will be charged for a full month on the day you enable origin shielding, dedicated IP addressing, or log export. Also, a fee is charged for the included outgoing traffic package on the day the CDN resource is created. Thereafter, you will be charged on the first day of every next month.

You can choose one of the following billing models when activating dedicated IP addressing:

• Per individual CDN resource. This option is cost-effective if you have few CDN resources or need dedicated IP addresses only for some of them.
• For all CDN resources of your billing account. This is optimal if you need dedicated IP addresses for multiple CDN resources.