Skip to content

Commit 7f51fbf

Browse files
committed
units
1 parent 32b0dd9 commit 7f51fbf

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/internet-peering/policy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Microsoft maintains a selective peering policy designed to ensure the best possi
4747
* The locations where you can connect with Microsoft for Direct peering or Exchange peering are listed in [PeeringDB](https://www.peeringdb.com/net/694)
4848

4949
* **Exchange peering:**
50-
* Peers are expected to have at minimum a 10 Gb connection to the exchange.
50+
* Peers are expected to have at minimum a 10 Gbps connection to the exchange.
5151
* Peers are expected to upgrade their ports when peak utilization exceeds 50%.
5252
* Microsoft encourages peers to maintain diverse connectivity to exchange to support failover scenarios.
5353

@@ -60,8 +60,8 @@ Microsoft maintains a selective peering policy designed to ensure the best possi
6060

6161
## Traffic requirements
6262

63-
* Peers over Exchange peering must have at minimum 500 Mb of traffic and less than 2 Gb. For traffic exceeding 2 Gb, Direct peering should be established.
64-
* Microsoft requires at minimum 2 Gb for direct peering. Each mutually agreed to peering location must support failover that ensures peering remains localized during a failover scenario.
63+
* Peers over Exchange peering must have at minimum 500 Mb of traffic and less than 2 GB. For traffic exceeding 2 GB, Direct peering should be established.
64+
* Microsoft requires at minimum 2 GB for direct peering. Each mutually agreed to peering location must support failover that ensures peering remains localized during a failover scenario.
6565

6666
## Next steps
6767

0 commit comments

Comments
 (0)