|
| 1 | +--- |
| 2 | +title: Network bandwidth |
| 3 | +titleSuffix: Azure Cosmos DB |
| 4 | +description: Review how Azure Cosmos DB ingress and egress operations influence Azure network bandwidth consumption. |
| 5 | +author: seesharprun |
| 6 | +ms.author: sidandrews |
| 7 | +ms.reviewer: garyhope |
| 8 | +ms.service: cosmos-db |
| 9 | +ms.topic: conceptual |
| 10 | +ms.date: 01/19/2024 |
| 11 | +--- |
| 12 | + |
| 13 | +# Azure Cosmos DB network bandwidth |
| 14 | + |
| 15 | +Azure Cosmos DB is a globally distributed database system that allows you to read and write data from the local replicas of your database. Azure Cosmos DB transparently replicates the data to all the regions associated with your Azure Cosmos DB account. |
| 16 | + |
| 17 | +To move your database requests and responses between the Cosmos DB account and the application, which connects it requires Azure network bandwidth. Cosmos DB also uses Azure network bandwidth to replicate data between Cosmos DB regions when you select multiple regions for your Cosmos DB account. |
| 18 | + |
| 19 | +Azure Cosmos DB bills for data that leaves the Azure cloud to any destination on the internet or transits the Azure WAN between Azure regions. |
| 20 | + |
| 21 | +| Data Transfer In (Ingress) | All GB / Month | |
| 22 | +| --- | --- | |
| 23 | +| Data transfer into any region | Not billed | |
| 24 | +| Data transfer within any region | Not billed | |
| 25 | +| Data transfer within an availability zone or between availability zones within any region | Not billed | |
| 26 | + |
| 27 | +| Data Transfer Out (Egress) | First 5 GB / Month | > 5 GB / Month | |
| 28 | +| --- | --- | --- | |
| 29 | +| Data transfer from any region in Europe or North America to any other regions or any destination on the internet | Not billed | Billed | |
| 30 | +| Data transfer from any region in Asia or Oceania or Middle East and Africa to any other region or any destination on the internet (excluding China) | Not billed | Billed | |
| 31 | +| Data transfer from any region in South America to any other region within the same continent or across continents or any destination on the internet | Not billed | Billed | |
| 32 | +| Data transfer from any region in China to any other region within the same continent or across continents or any destination on the internet | Not billed | Billed | |
| 33 | + |
| 34 | +## Billing meter details |
| 35 | + |
| 36 | +The following are the recently introduced Azure Cosmos DB Bandwidth billing meter details along with the previous meter identifiers from which Azure Cosmos DB Bandwidth moved. |
| 37 | + |
| 38 | +| New Meter Name | New Meter Type | New Meter ID | Previous Meter ID | |
| 39 | +| --- | --- | --- | --- | |
| 40 | +| Inter Region Data Transfer In | Data Transfer In (GB) | 415e7499-ea3b-5b45-8a9c-80a141aa262 | d8831a85-697a-4d43-acec-8e1599f58b5d | |
| 41 | +| Inter Region Data Transfer In | Data Transfer In (GB) | ffa692fd-9d68-5f7c-a4b3-2644fe8ddb4 | 3a9d164b-d3c1-4350-9945-fa8056700299 | |
| 42 | +| Inter Region Data Transfer In | Data Transfer In (GB) | adae3632-6f0c-5bc0-b864-b6a7b437438 | 32c3ebec-1646-49e3-8127-2cafbd3a04d8 | |
| 43 | +| Inter Region Data Transfer In | Data Transfer In (GB) | b25ed7ec-9731-59f1-a0fb-d3327646847 | 42bb05e1-6f42-4de1-a6ba-7ffb976cb56 | |
| 44 | +| Inter Region Data Transfer In | Data Transfer In (GB) | 8f44fdc5-8992-5838-b309-8a101b97576 | e315c24e-2f54-4668-95ae-5aef18f93125 | |
| 45 | +| Inter Region Data Transfer Out | Data Transfer Out (GB) | 475ec5dc-3ce0-526d-a38f-0868db1a8fb | 3730eb6d-75a1-4e4b-82a2-383264ebffd8 | |
| 46 | +| Inter Region Data Transfer Out | Data Transfer Out (GB) | 08339433-af53-57f7-87ee-22a39c0f35c | 6c5c3140-e894-4ecf-aacc-60137b0bc93b | |
| 47 | +| Inter Region Data Transfer Out | Data Transfer Out (GB) | dffc0580-fe39-515f-86af-7a5cf75b74d | 9995d93a-7d35-4d3f-9c69-7a7fea447ef4 | |
| 48 | +| Inter Region Data Transfer Out | Data Transfer Out (GB) | 722e5945-90e6-59b3-8ed2-412d73c3984 | fe167397-a38d-43c3-9bb3-8e2907e56a41 | |
| 49 | +| Inter Region Data Transfer Out | Data Transfer Out (GB) | dc9930dd-f096-5af1-8467-ba15cf7232d | c089a13a-9dd0-44b5-aa9e-44a77bbd6788 | |
| 50 | + |
| 51 | +## Frequently asked questions |
| 52 | + |
| 53 | +Here's a list of commonly asked questions for this service. |
| 54 | + |
| 55 | +- **Will the change to new Meters cost me more for Azure Cosmos DB bandwidth?** |
| 56 | + |
| 57 | + - No, whilst the new meters are no longer tiered, the new meter billing rate is equal to or lower than the least expensive tier of the previous meters. Most Cosmos DB accounts see a reduction in Azure Cosmos DB bandwidth costs. |
| 58 | + |
| 59 | +- **Do I get any network bandwidth every month at no cost?** |
| 60 | + |
| 61 | + - Yes, Azure Cosmos DB includes 5 GB of network bandwidth per month. |
| 62 | + |
| 63 | +- **Will I still see the previous meters on my bill after Azure Cosmos DB moves to the new meters?** |
| 64 | + |
| 65 | + - It depends, you could continue to see previous meters on your Azure bill as they continue to be used by some other Azure Services. You could see Azure Cosmos DB bandwidth billing disabled for a short period during the transition. You aren't double charged during the transition. |
| 66 | + |
| 67 | +- **Will a region failover impact my egress data?** |
| 68 | + |
| 69 | + - It can, when your Azure Cosmos DB account is failed over to new region all traffic is automatically redirected to this new region. If this region is now different from where your Azure Cosmos DB client is located it results in data egress between the regions. |
| 70 | + |
| 71 | +## Next step |
| 72 | + |
| 73 | +> [!div class="nextstepaction"] |
| 74 | +> [If you have additional questions or feedback on Cosmos DB networking](mailto:[email protected]) |
0 commit comments