Skip to the yard
Waxsealai

Cloudflare Opens Private Origins Routing to More Customers

Shipped
Shipper
Enrique Somoza
Readers
761

Cloudflare can apply WAF, caching, bot management and Workers to private origins over existing network connections, with setup and routing requirements.

Cloudflare Opens Private Origins Routing to More Customers

Cloudflare’s private origins service lets teams put its application services in front of servers that keep private IP addresses. With general availability, access extends beyond the customers who joined the closed beta. A proxied DNS record can send requests to a private origin over existing Cloudflare One connectivity, while Cloudflare handles the application traffic on its network.

The practical change is that private APIs, agent backends, MCP servers and operational tools can receive traffic from partners, customers or agents without making their origins directly reachable from the public Internet. Teams can use the same WAF, caching, bot management and Workers capabilities they use with public origins. Rate limiting and traffic transformation rules are also available.

Private origin, familiar application controls

Previously, putting Cloudflare in front of a service that wasn’t built for direct Internet access could require exposing a public IP, opening a firewall port or running cloudflared alongside the origin. Those steps could make it harder to apply the same traffic protections and controls used for public applications.

With private origins, the DNS record points to the origin’s private address, and Cloudflare routes the connection over the customer’s existing private network path. The origin retains its private IP, and the setup doesn’t require an inbound firewall exception. For Cloudflare WAN connections, there’s no connector software to install on the origin. Cloudflare Mesh uses a connector within the private network, which can serve multiple origins.

Supported application services include WAF and managed rules, bot management, rate limiting, caching, transform and rewrite rules, and Workers. Some features aren’t available: Argo Smart Routing and Dedicated CDN Egress IPs are unsupported. Origin health checks require Load Balancing. The developer documentation lists the current limitations.

DNS record controls the route

Setup starts with a proxied A or AAAA record for the origin. Cloudflare automatically enables private network routing when the address falls within supported private ranges: RFC 1918 private IPv4, RFC 6598 CGNAT addresses (100.64.0.0/10), or RFC 4193 unique local IPv6 (fc00::/7). For these ranges, the setting can’t be disabled; an API attempt to turn it off returns an error. If the origin has a public IP that is reachable only through the private network, routing can be enabled manually.

The rest of the request path remains familiar. TLS termination, WAF processing, rules and caching continue to run on Cloudflare’s network. The routing setting tells Cloudflare how to reach the origin; it doesn’t replace the application services applied to the request.

For automated DNS configuration, private routing is an attribute on a standard record:

POST /zones/{zone_id}/dns_records
{
  "type": "A",
  "name": "app.example.com",
  "content": "10.0.0.50",
  "ttl": 300,
  "proxied": true,
  "private_routing": true
}

Cloudflare’s proxy platform uses its Origin API to determine where to send traffic. The response includes the destination address and whether it should be reached over a private path:

{
  "zone_name": "example.com",
  "ipv4_addresses": ["10.0.0.50"],
  "private_routing": true
}

When that flag is present, the proxy hands the connection to Cloudflare’s private networking layer instead of trying to reach the private address over the public Internet. The route uses existing connectivity, which can include IPsec, GRE, Cloudflare Tunnel, CNI or Cloudflare Mesh.

Requirements and setup checks

Accounts need the Private Origins entitlement, enabled through the account team, and Cloudflare One connectivity using one of the supported network paths. Unified Routing must also be enabled unless the connection uses Cloudflare Tunnel, which doesn’t require it. Accounts can arrange an upgrade through their account team.

For Cloudflare WAN or Cloudflare Mesh, teams need a return route for Cloudflare’s source ranges: 100.64.0.0/12 for IPv4 and 2606:4700:cf1:5000::/64 for IPv6. After creating the proxied record, confirm that “Use private network routing” is enabled. Existing WAF, cache and bot management settings apply to the hostname without additional changes.

Timeouts with no requests reaching the origin are a sign to check routing in both directions. During the beta, a missing return route for Cloudflare’s source range was the most common setup failure. The setup guide covers the full configuration.

Scope of the release

The available service handles public traffic reaching private origins. Cloudflare is also working on private-to-private traffic, where users, services and AI agents on private networks reach applications on other private networks through Cloudflare’s application services. Engineering work is underway, with a closed beta targeted for early 2027.

That planned extension would apply controls such as WAF, rate limiting and bot management to internal destinations such as wiki.company.internal, as well as to service-to-service traffic between clouds and data centers. For now, private origins gives teams a way to keep origin addresses private while applying Cloudflare’s existing application services to requests arriving from outside their networks.

Source: Enrique Somoza · blog.cloudflare.com

Same vesselRelated cargo