• Sources: primary
  • Summary: On 2026-10-30 Cloudflare made private origins generally available: a proxied A or AAAA record pointing at an RFC 1918, CGNAT or fc00::/7 address is routed over IPsec, GRE, CNI, Cloudflare Tunnel or Cloudflare Mesh with WAF, bot management, rate limiting, caching and Workers applied. Argo Smart Routing and Dedicated CDN Egress IPs are not supported, and WAN or Mesh users must add return routes for 100.64.0.0/12 and 2606:4700:cf1:5000::/64. A private-to-private closed beta is targeted for early 2027.
  • Why it matters: Internal APIs and MCP servers can sit behind Cloudflare's edge without a public IP or inbound firewall hole, but a missing return route was the most common setup failure in the beta.
  • Follow-up: Private-to-private traffic closed beta targeted for early 2027.