Cloudflare services for private origins is now generally available
Web page · https://blog.cloudflare.com/private-origins-public-to-private
Public traffic to private origins, with WAF, bot management, caching, and Workers, is now available to every customer with Cloudflare One connectivity.
First seen by Oriel on .
AI summary
Cloudflare services for private origins is generally available, letting proxied DNS records reach private IP origins over existing Cloudflare One connectivity while retaining Cloudflare application protections.
- Supported services include WAF and managed rules, bot management, rate limiting, caching, transform and rewrite rules, and Workers.
- Private routing activates automatically for RFC 1918, RFC 6598, and RFC 4193 address ranges; it can be enabled manually for public IPs reachable only through a private network.
- Routing uses a `private_routing` DNS-record attribute to send proxy traffic through existing IPsec, GRE, Cloudflare Tunnel, CNI, or Cloudflare Mesh connectivity.
- Setup requires the Private Origins entitlement and Cloudflare One connectivity; Unified Routing is also required except when using Cloudflare Tunnel.
- Argo Smart Routing and Dedicated CDN Egress IPs are unsupported, and origin health checks require Load Balancing; Cloudflare is targeting a private-to-private traffic closed beta in early 2027.
#cloudflare #private networking #dns #web application firewall
Generated by gpt-5.6-sol. Check the original for details.
Aliases
| Source | External ID | URL |
|---|---|---|
| Cloudflare Blog | 01M64V2TDYZYSS8RE60T3MWKSM | https://blog.cloudflare.com/private-origins-public-to-private/ Read discussion |