Cloudflare Tunnels: 1,000 Included, Then $4.50 per Extra Tunnel

Count tunnels and routes separately

On October 16, Cloudflare announced that the default route limit rose from 1,000 to 50,000 per account. It covers CIDR and hostname routes for Cloudflare Tunnel and Cloudflare Mesh, and applies automatically without an account change.

A route is an entry that connects a network or hostname; it is not a tunnel. Tunnel and Mesh routes share the 50,000-entry ceiling, so both kinds of routes belong in the same account-level count.

Public hostnames, which Cloudflare calls published applications, do not count as routes. Published applications have their own per-tunnel limit, so do not add them to the route total or mistake 50,000 routes for 50,000 tunnels.

The first 1,000 tunnels are included

Each Cloudflare account includes 1,000 tunnels. Tunnels for Platforms lets an account add more capacity as its fleet grows, without splitting that fleet across multiple accounts just to stay under the standard tunnel limit.

Cloudflare lists self-serve additional capacity at $4.50 per extra tunnel per month. Enterprise customers can ask their account team about committed capacity or usage-based billing; the documentation does not publish one universal price for those arrangements.

The charge is tied to the additional tunnel capacity purchased. When planning one tunnel per device, end customer, or temporary development environment, compare the number you need to keep with the included 1,000 and review the order summary before activating more.

Inactive tunnels still use capacity

Every tunnel that exists in the account counts, including one marked inactive or one with no connected cloudflared replicas. Stopping a process or disconnecting its replica does not free the tunnel slot; delete tunnels that are no longer needed.

Reducing a subscription does not delete existing tunnels. If the new limit is lower than the number already in the account, those tunnels continue to work, but Cloudflare blocks new tunnel creation until you delete enough objects or buy more capacity.

When an account reaches its current tunnel limit, existing tunnels and their connections are not affected by the limit itself. The failed operation is the request to create another tunnel, which matters for systems that create temporary environments automatically.

Add or change capacity in the dashboard

To add capacity, open Networking → Tunnels in the Cloudflare dashboard and choose Buy more tunnels in the Usage card. Enter the additional amount, review the order summary and payment method, then activate it. Cloudflare says the new limit appears in the card within a few minutes.

To change or cancel the subscription, go to Manage Account → Billing → Subscriptions and find Tunnels for Platforms. Changing the purchased amount changes the creation limit; it does not remove existing tunnel objects.

Before changing the limit, compare your own device, customer, or environment inventory with the tunnels listed in the account. Cloudflare recommends reconciling that list regularly and deleting tunnels that no longer belong to an active device, customer, or environment.

Estimate the extra capacity with a hypothetical example

Suppose an account plans to keep 1,004 tunnels and uses the public self-serve monthly price. Four are above the included 1,000, so the listed estimate is 4 × $4.50, or $18 per month. This example demonstrates the arithmetic; it is not a quote or a prediction of a particular account's invoice.

Before buying, check three limits independently: the shared 50,000-route account cap, the number of tunnels in the account, and the published-application limit per tunnel. Spare room in one category does not establish that the others have room.