From 0b280fff22f5111ceb6c090c9fd4c8b4d1f8bbe5 Mon Sep 17 00:00:00 2001 From: Satish Date: Thu, 6 Nov 2025 16:51:04 +1100 Subject: [PATCH] Clarify virtual hub router throughput limitations Added note about performance degradation for TCP flows exceeding 1.5 Gbps in a single TCP flow as mentioned in https://learn.microsoft.com/en-us/azure/virtual-wan/hub-settings Its better to state that in the main page. --- articles/virtual-wan/virtual-wan-about.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/virtual-wan/virtual-wan-about.md b/articles/virtual-wan/virtual-wan-about.md index 383bf4d271694..929bf9732daac 100644 --- a/articles/virtual-wan/virtual-wan-about.md +++ b/articles/virtual-wan/virtual-wan-about.md @@ -112,7 +112,7 @@ Virtual WAN allows transit connectivity between VNets. VNets connect to a virtua [!INCLUDE [virtual hub router status](../../includes/virtual-wan-hub-router-status.md)] -Every virtual hub router supports an aggregate throughput up to 50 Gbps. +Every virtual hub router supports an aggregate throughput up to 50 Gbps. However, traffic may experience performance degradation if more than 1.5 Gbps is sent in a single TCP flow. See [About virtual hub settings](https://learn.microsoft.com/azure/virtual-wan/hub-settings) for details. Connectivity between the virtual network connections assumes, by default, a maximum total of 2000 VM workload across all VNets connected to a single virtual hub. **Hub infrastructure units** can be adjusted to support additional VMs. For more information about hub infrastructure units, see [Hub settings](hub-settings.md).