- Which geographic areas correspond to Zone 1 and Zone 2 for CDN data transfers?
CDN data transfer pricing is based on the CDN node location from where the transfers are served, not the end user’s location. The following geographic areas correspond to Zone 1 and Zone 2 for CDN.
Zone 1: North America and Europe
- US East: Atlanta, Miami, New York, Washington D.C.
- US North Central: Chicago
- US South Central: Dallas
- US West: Los Angeles, San Jose, Seattle
- Europe North: Copenhagen, Helsinki, Stockholm, Vienna, Warsaw
- Europe West: Amsterdam, Frankfurt, Milan, London, Madrid, Paris
Zone 2: Latin America, Middle East, Africa and Asia Pacific
- Asia Pacific East: Batam, Hong Kong, Jakarta, Kaohsiung, Singapore
- Asia Pacific Southeast: Melbourne, Sydney
- Japan East: Tokyo
- Japan West: Osaka
- Once my data transfers exceed 10TB per month, are they all billed at the rate for the higher tier?
No. Usage falls under each tier is billed at the rate for that tier. For example, if you use 50TB of data transfer in Zone 1, 10 TB will be billed at $0.12 per GB and the next 40 TB will be billed at $0.08 per GB.
- Can I specify which CDN data center I use to serve the end users?
No. The CDN data center is selected based on the end users’ network configurations and cannot be controlled by the developer. Users may be served by locations that are preferred by their ISP, or nodes that are "closer" in a logical sense, not necessarily in physical proximity.
- Do the CDN charges include requests to Storage to retrieve the data and data transfers from Storage to CDN location?
No. When the CDN receives a request for an object that is not at an edge location, it makes a request to Azure Storage to obtain the data. The cost of reading data from Storage and transferring data from Storage to CDN is based on regular Storage and Data Transfer charges.
- What impacts the availability of content in CDN’s local caches, and how can I reduce the need to make frequent origin requests?
Availability of content in CDN's local caches (often called "cache efficacy" or "offload") is influenced by multiple factors including:
- Expiration ("max-age") header values
- Overall total size of the developer's content library (how much could be cached)
- Active working set (how much is currently cached)
- Traffic (how much is being served)
- Cache churn (how often are objects being added to cache, or aging out)
For example, a developer with high churn and high traffic has less cache efficacy than other users because objects are swapped in and out more frequently. This incurs higher Storage and Data Transfer charges since more origin requests are required.
To reduce the need to make origin requests, you can make longer max-age headers, allowing CDN to hold objects longer.
CDN service is available in the following regions. CDN nodes are available in 29 locations worldwide.
|Geo ||Regions |
| United States || East US , North Central US , South Central US , West US |
| Europe || North Europe , West Europe |
| Asia Pacific || East Asia , Southeast Asia |
| Japan || Japan East , Japan West |
| Australia || Australia East , Australia Southeast |
Support and SLA
We provide technical support for all Azure services released to General Availability, including CDN, through Azure Support, starting at $--/month. Billing and subscription management support is provided at no cost.
We guarantee that at least 99.9% of the time CDN will respond to client requests and deliver the requested content without error. We will review and accept data from any commercially reasonable independent measurement system that you choose to monitor your content. You must select a set of agents from the measurement system’s list of standard agents that are generally available and represent at least five geographically diverse locations in major worldwide metropolitan areas. To learn more about our SLA, please visit the SLA page.