“Reserved route ports quota exceeded for organization” when creating routes in Tanzu Application Service

Products

• VMware Tanzu Platform Core

Issue/Introduction

When pushing an application or creating a route in Tanzu Application Service (TAS) for VMs, the following error is returned:

Reserved route ports quota exceeded for organization '<org-name>'

This error may appear even in newly created organizations and spaces, and even when no routes are currently listed:

cf routes 
No routes found.

The message may be confusing because it does not explicitly mention TCP routing.

Environment

Elastic Application Runtime (EAR) (formerly VMware Tanzu Application Service (TAS) for VMs)

Cause

The error occurs when attempting to create a TCP route, and the organization’s quota for reserved route ports is set to zero or has been exhausted.

In Cloud Foundry, HTTP and TCP routes are governed by different quota limits:

Quota Type	Applies To	Description
routes	HTTP routes	Total number of HTTP routes allowed
reserved-route-ports	TCP routes	Number of TCP ports that can be reserved

Each TCP route reserves a port and consumes one unit from the organization’s reserved-route-ports quota.

For example, a manifest containing:

routes:
  - route: example.domain.com:13306
    protocol: tcp

creates a TCP route and attempts to reserve port 13306.

If the organization quota (cf org-quotas) shows 0 for the column route ports:

name      total memory   instance memory   routes   service instances   paid service plans   app instances   route ports   log volume per second
default   10G            unlimited         1000     100                 allowed              unlimited       0             unlimited

then any TCP route creation attempt will fail with:

Reserved route ports quota exceeded for organization

This validation occurs before other checks (such as TCP router availability or domain type), which can make the message appear misleading.

Resolution

1. Confirm Organization Quota

Check the assigned quota plan with cf org-quotas and check that router ports if 0

2. Determine Whether TCP Routing Is Intended

If TCP routing is not required:

• Remove protocol: tcp

• Remove :port from the route definition

• Use a standard HTTP route:

routes:
  - route: app.example.domain.com

HTTP routes consume from the routes quota, not route ports.

3. Increase Reserved Route Ports Quota (if TCP is required)

A platform administrator can update the quota plan:

cf update-org-quota <quota-name> --reserved-route-ports <number>

Example:

cf update-org-quota default --reserved-route-ports 5

After updating the quota, retry the route creation.

4. Verify TCP Router Is Installed (if applicable)

TCP routes require the TCP Router component to be installed and configured in Ops Manager.
If TCP routing is not enabled at the platform level, TCP routes cannot be used even if quota is increased