Skip to content

Commit dcdbc45

Browse files
committed
updates to tabs
1 parent 79fa00d commit dcdbc45

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/networking/azure-network-latency.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,12 @@ The latency measurements are collected from Azure cloud regions worldwide, and c
1919

2020
## Round-trip latency figures
2121

22-
The monthly Percentile P50 round trip times between Azure regions for a 30-day window are shown as follows.
22+
The monthly Percentile P50 round trip times between Azure regions for a 30-day window are shown in the following tabs. The latency is measured in milliseconds (ms).
23+
24+
> [!IMPORTANT]
25+
> Monthly latency numbers across Azure regions do not change on a regular basis. Given this, you can expect an update of these tables every 6 to 9 months. Not all public Azure regions are listed in the tables below. When new regions come online, we will update this document as soon as latency data is available.
26+
>
27+
> You can perform VM-to-VM latency between regions using [test Virtual Machines](../virtual-network/virtual-network-test-latency.md) in your Azure subscription.
2328
2429
#### [North America / South America](#tab/Americas)
2530

@@ -669,9 +674,6 @@ Listing of Middle East / Africa regions including UAE, South Africa, and Qatar.
669674

670675
---
671676

672-
> [!IMPORTANT]
673-
> Monthly latency numbers across Azure regions do not change regulary. Given this, you can expect an update of this table every 6 to 9 months outside of the addition of new regions. When new regions come online, we will update this document as soon as data is available.
674-
675677
## Next steps
676678

677679
Learn about [Azure regions](https://azure.microsoft.com/global-infrastructure/regions/).

0 commit comments

Comments
 (0)