Yandex Cloud CDN release notes

Written by

Updated at August 5, 2026

Q2 2026

Cloud CDN is now available in the Kazakhstan region.
Updated the pricing model.
Added resource-based pricing for dedicated IP addressing.
Introduced a limit on the number of dedicated IP addresses for CDN resources per billing account.
Extended the list of HTTP methods blocked by default in client requests: aside from POST, now PUT, PATCH, and DELETE are also blocked. For more on activating methods, see Requests with the POST, PUT, PATCH, and DELETE methods are not available to users.
Extended the network of our points of presence: the Russia region now has 65 PoPs with a total throughput exceeding 7 Tbps.
Fixed errors related to the Terraform provider.
Improved the management console interface:
- Moved the following fields to the origin settings section:
  - Origin request protocol
  - Origin domain name
  - Host header
- Moved these fields to a dedicated tab, Security:
  - Redirect clients
  - Access via secure token
  - Limit access by IP address
  - IP-based access
- Improved error display in wizard steps when creating a CDN resource and origin group. Now you see each error on the actual step where it occurred.
- If you select an L7 load balancer as an origin, the drop-down list now displays only load balancers that have public IP addresses linked.

Now you can specify a different origin for a CDN resource in location rules without inheriting settings from the main configuration.
Implemented TLS security profiles for a CDN resource, containing certain allowed TLS ciphers.
Added support for configuring a custom server name for SNI.
In the management console, implemented the ability to configure for a CDN resource the allowed HTTP POST method in client requests as well as WebSocket support. To activate these options, contact support. For more information, see Requests with the POST, PUT, PATCH, and DELETE methods are not available to users and How do I enable WebSocket support?.
Added an HTTP response configuration option to set a code for a CDN resource redirect or a static response code with a predefined response body.
Added a CDN resource blocking status indicator to the management console. The status is displayed if the CDN resource has been blocked for violating the terms of use.
Now you can set a custom content caching duration.
Now you can set up how to follow request redirects in the management console.

Implemented location rules, a mechanism used to selectively redefine CDN resource settings for requests whose paths match a specific pattern.
Now you can enable a CDN resource to follow request redirects from the origin. With this feature on, Cloud CDN sends a request to the address specified in the origin response and then returns content from the target address to the client.
Added support for the WebSocket protocol. To enable the feature, contact support.
Added new points of presence.
Supported the pricing calculator for Cloud CDN.
Added an Audit Trails management event, ResourceDelete, for deleting a CDN resource.

Added a Yandex Cloud CDN provider based on Yandex's proprietary technology.
You can now select a provider when creating a resource or origin group.
Updated the CDN resource creation interface:
- Creating and configuring a resource through the wizard are made simpler.
- You can now duplicate the configuration of an existing CDN resource.
Added functionality to manage resource use rules for the Yandex Cloud CDN provider. This setting is available in the API.
Fixed bugs related to Terraform:
- Incorrect display of the provider_cname resource domain name.
- Not being able to select a provider for a resource.

Added the option to assign Yandex Resource Manager labels to CDN resources.

Added the request redirection feature. This setting is available in the management console, CLI, and API.
Added support for setting up an IP-based access policy in the management console.

You can now configure secure token access in the management console.

Added support for IP-based access policies for CDN resources.
Implemented a system for restricting access to a CDN resource using secure tokens.
Removed support for automatic issue of TLS certificates for CDN resources by the EdgeCenter CDN provider. Now, you must pre-upload TLS certificates to Yandex Certificate Manager. For more information, see Configuring TLS certificates for HTTPS connections between clients and the CDN.