cloudflare · angelampcosta · Apr 14, 2025 · Mar 27, 2025
@@ -52,3 +52,5 @@ Private Network Load Balancing on-ramps, on the other hand, refer to secure path
 * **Requests originating from the public Internet and directed to a private/internal service**: You can route requests from the Internet to your internal services on internal IPs - such as accounting or production automation systems - using [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/).
 
 * **Intelligent traffic routing**: Benefit from failover for your private traffic and have the ability to monitor the health of these IP targets directly, rather than load balancing to a tunnel and only monitoring the health of the tunnel itself.
+
+* **Host applications on non-standard ports**: Easily specify and route traffic to applications hosted on private IP addresses using non-standard ports, allowing greater flexibility in service configuration without requiring changes to existing infrastructure.
@@ -22,6 +22,7 @@ You can create a pool within the [load balancer workflow](/load-balancing/load-b
    * (Optional) A [**Virtual Network**](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/). Required when the endpoint has a private IP address.
    * A [**Weight**](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights)
    * (Optional) A [hostname](/load-balancing/additional-options/override-http-host-headers/) by clicking **Add host header**
+   * (Optional) The destination port to which the traffic will be served.
 
 :::note[Note]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -52,3 +52,5 @@ Private Network Load Balancing on-ramps, on the other hand, refer to secure path
		* Requests originating from the public Internet and directed to a private/internal service: You can route requests from the Internet to your internal services on internal IPs - such as accounting or production automation systems - using [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/).

		* Intelligent traffic routing: Benefit from failover for your private traffic and have the ability to monitor the health of these IP targets directly, rather than load balancing to a tunnel and only monitoring the health of the tunnel itself.

		* Host applications on non-standard ports: Easily specify and route traffic to applications hosted on private IP addresses using non-standard ports, allowing greater flexibility in service configuration without requiring changes to existing infrastructure.