Cloudflare raises Tunnel and Mesh route capacity to 50,000 per account

On 16 October 2026, Cloudflare announced that account route capacity for Cloudflare Tunnel and Mesh increased from 1,000 to 50,000 routes. Changelog announcement

What changed

The higher 50,000-route ceiling applies to CIDR and hostname routes configured for Cloudflare Tunnel and Mesh at the account level. Public application hostnames are excluded from this count.

Why the distinction matters for BYOIP teams

Network teams running both private-network overlays and public prefix announcements on Cloudflare should keep this account limit separate from Magic Transit and Cloudflare WAN's BGP routing limits.

The 50,000-route figure governs CIDR and hostname entries in Cloudflare Tunnel and Mesh. It does not raise the 5,000-route inbound BGP routing-information-base (RIB-in) limit that applies to GRE and IPsec tunnel peering in Magic Transit and Cloudflare WAN, which is enforced before inbound BGP route filters run. See our coverage of Cloudflare's 15 October BGP route filter profiles and our Cloudflare BYOIP integration profile for how tunnel BGP sessions are governed.

What to check

• Keep Tunnel and Mesh private-routing tables distinct from Magic Transit or Cloudflare WAN BGP prefix inventories when planning capacity.
• Verify whether routes are configured as Tunnel/Mesh CIDR or hostname routes, public application hostnames, or GRE/IPsec BGP advertisements before relying on the 50,000-route allowance.
• Review Cloudflare's product-limit documentation directly before making fleet-sizing decisions.