Cloudflare Launches Private Origins General Availability for Secure Routing
Cloudflare's private origins feature is now generally available, enabling application services over existing private network connections without public IP exposure.
Before you start: versions, package names and storage identifiers change over time. Check the commands against the official documentation for your setup before running them, especially anything that creates, deletes or overwrites data.
Private Origins Reach General Availability
Cloudflare announced the general availability of its private origins service, allowing organizations to route traffic securely to private IP addresses via existing Cloudflare One connections. The release affects eligible customers utilizing internal APIs, AI agent backends, MCP servers, and operational tools that require edge protections without public exposure.
Previously confined to a closed beta launched in June, the capability is now broadly accessible for accounts with the Private Origins entitlement. By pointing a proxied DNS record to a private IP, practitioners can secure internal applications using the same edge tools applied to public endpoints.
Practical Capabilities and Application Services
When routing traffic to a private origin, Cloudflare applies its standard application services stack. This includes the Web Application Firewall (WAF) with managed rules, bot management, rate limiting, caching, transform and rewrite rules, and Workers.
For supported private IP ranges—such as RFC 1918 private IPv4 addresses, RFC 6598 CGNAT addresses, and RFC 4193 unique local IPv6 addresses—private network routing is enabled automatically. For public IPs that are reachable solely through a private network, administrators can enable the setting manually. Deployments can also be managed programmatically via the API by adding a private_routing attribute to standard DNS record creation payloads.
Connectivity Requirements and Current Limits
Using the feature requires active Cloudflare One connectivity via IPsec, GRE, CNI, Cloudflare Tunnel, or Cloudflare Mesh. Accounts utilizing Cloudflare WAN or Cloudflare Mesh must configure a return route for specific source ranges: 100.64.0.0/12 for IPv4 and 2606:4700:cf1:5000::/64 for IPv6, as missing return routes are a common source of timeout errors.
Certain limits remain active at launch. Argo Smart Routing and Dedicated CDN Egress IPs are not supported, and origin health checks necessitate Load Balancing. Furthermore, the private routing toggle cannot be turned off for standard private IP ranges through the API.
Source
Official announcement or documentation
Some links on this page may be affiliate links. If you buy through them we may earn a commission at no extra cost to you. See our affiliate disclosure.