Cloudflare Services for Private Origins: Architecture, API, and Implementation

Black computer keyboard – Cloudflare Services for Private Origins: Architecture, API, and Implementation

Overview of Cloudflare Services for Private Origins GA

Organizations routinely operate internal infrastructure—including proprietary APIs, AI agent backends, Model Context Protocol (MCP) servers, and operational dashboards—that must accept inbound traffic from third-party partners, remote agents, or customers over the public Internet. Historically, placing an edge security layer in front of these private workloads required allocating public IP addresses, opening inbound ports on perimeter firewalls, or installing and maintaining dedicated connector software directly alongside the origin application host.

With the general availability (GA) of Cloudflare services for private origins, organizations can map proxied DNS records directly to private IPv4 or IPv6 addresses. Public web traffic hits Cloudflare’s global edge, where application-level protections are executed before the request is securely forwarded over existing Cloudflare One private network connections. This architecture allows organizations to extend security, performance, and compute capabilities to internal backends without expanding their public attack surface.

Architectural Breakdown: Public Edge to Private Networking

The routing pipeline bridges Cloudflare’s public application proxy with its private network transport layer. When a client initiates a request to an enterprise domain backed by a private origin, the traffic follows a clear, multi-stage path:

  1. Edge Ingress & TLS Termination: The connection lands on Cloudflare’s public edge network. TLS termination occurs securely at the edge point of presence (PoP).
  2. Application Layer Execution: Before traffic leaves the edge proxy, standard Cloudflare application services process the request. These include:
    • Web Application Firewall (WAF): Managed rulesets inspect payloads for malicious signatures and vulnerabilities.
    • Bot Management & Rate Limiting: Automated traffic identification and volume constraints are enforced.
    • Caching & Edge Rules: Static assets are cached, and Transform/Rewrite rules modify request headers or URLs.
    • Cloudflare Workers: Serverless code runs at the edge to execute custom business logic before origin forwarding.
  3. Private Routing Handoff: Once edge processing completes, Cloudflare’s proxy platform queries an internal Origin API. If the target host has private routing enabled, traffic is passed to the Cloudflare One private networking layer instead of attempting standard public WAN egress.
  4. Private Transport Egress: The request travels through established private connectivity—such as IPsec, GRE, Cloudflare Network Interconnect (CNI), Cloudflare Tunnel, or Cloudflare Mesh—directly to the origin network.

Supported Network Technologies and Address Spaces

Cloudflare services for private origins automatically detects standard private network IP allocations. The platform natively enforces private routing for the following reserved IP address spaces:

  • RFC 1918 IPv4 Ranges: Standard private networks (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).
  • RFC 6598 CGNAT Ranges: Carrier-Grade NAT space (100.64.0.0/10).
  • RFC 4193 IPv6 Ranges: Unique Local IPv6 Addresses (fc00::/7).

When a proxied DNS record targets an IP within these ranges, the private_routing attribute is enabled automatically by default. To prevent accidental exposure or misrouting, this setting cannot be toggled off via the API for these reserved ranges; explicit attempts to set private_routing: false on an RFC 1918, RFC 6598, or RFC 4193 target will yield an API error.

In scenarios where an origin utilizes a public IP address that is strictly insulated and reachable only through a customer’s private network layer, administrators can manually toggle the private routing flag on the associated DNS record.

API Implementation and DNS Configuration

Automating infrastructure through the Cloudflare REST API requires adding a single standard boolean field to the DNS record configuration payload. Below is an example of creating a proxied A record mapped to an internal IPv4 host:

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

When the proxy platform handles incoming HTTP/HTTPS requests for app.example.com, it issues an internal lookup to Cloudflare’s Origin API. The service returns a structured metadata response indicating the private transport requirement:

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

Upon reading "private_routing": true, the proxy platform redirects packet delivery from standard Internet routing to the Cloudflare One overlay network corresponding to that enterprise account.

Setup Prerequisites and Routing Requirements

Before mapping proxied public DNS records to private IP destinations, administrators must ensure their account and network topology fulfill the following technical prerequisites:

  • Private Origins Entitlement: The feature flag must be provisioned on the Cloudflare account via the account management team.
  • Established Cloudflare One Connectivity: At least one active transport mechanism must be configured (IPsec tunnel, GRE tunnel, Cloudflare Network Interconnect, Cloudflare Tunnel, or Cloudflare Mesh).
  • Unified Routing: Unified Routing must be active across the account infrastructure. This requirement applies to all connectivity types except standard cloudflared Tunnels, which operate independently of Unified Routing.
  • Return Route Configuration: For connections established over Cloudflare WAN (IPsec/GRE/CNI) or Cloudflare Mesh, internal network routers and firewalls must be explicitly configured with return routes for Cloudflare source egress ranges.

Network Troubleshooting: Addressing Common Setup Failures

During deployment, the single most frequent cause of connection failures and request timeouts is an incomplete network return path. When Cloudflare routes a request over an IPsec or GRE path into a private network, the egress source IP originates from Cloudflare’s designated internal CGNAT and IPv6 source blocks.

If perimeter firewalls or local subnets lack routes pointing back through the established Cloudflare WAN connection, the origin host receives the SYN packet but drops or misroutes the SYN-ACK response.

To resolve routing timeouts, ensure that all internal routing tables specify the next-hop back to Cloudflare for the following exact source ranges:

  • IPv4 Source Range: 100.64.0.0/12
  • IPv6 Source Range: 2606:4700:cf1:5000::/64

Current Feature Limitations and Operational Boundaries

While services for private origins allows full application layer control over private IP targets, certain global performance and traffic distribution mechanisms remain restricted in the current release:

  • Argo Smart Routing: Argo optimization models are currently unsupported for traffic bound to private origins.
  • Dedicated CDN Egress IPs: Requests egressing toward private origins cannot be configured to use fixed Dedicated CDN Egress IP allocations.
  • Origin Health Checks: Standalone health monitoring probes directed at private IPs are not supported; health checks must be deployed using Cloudflare Load Balancing modules.

Roadmap: Extending Controls to Private-to-Private Traffic

The current general availability release specifically addresses public-to-private connection topology—allowing external users, partner networks, and public agents to securely query private internal origins.

The next phase of development focuses on internal, private-to-private traffic patterns. This planned capability will allow internal users, microservices, and autonomous AI agents connected inside private enterprise networks to communicate with internal applications on distinct private networks while passing through Cloudflare’s application services. Engineering for this architecture is underway, with a targeted closed beta scheduled for early 2027.

Frequently asked questions

What is Cloudflare services for private origins?

It is a feature that allows proxied Cloudflare DNS records to point directly to private IP addresses. This enables Cloudflare edge security and performance services—such as WAF, bot management, caching, and Workers—for private origins without exposing public IP addresses or opening inbound firewall ports.

Which private IP address ranges are automatically supported?

Private network routing is automatically enabled for RFC 1918 IPv4 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), RFC 6598 CGNAT addresses (100.64.0.0/10), and RFC 4193 unique local IPv6 addresses (fc00::/7).

What underlying connectivity is required to route traffic to private origins?

You must have active Cloudflare One connectivity established, such as IPsec tunnels, GRE tunnels, Cloudflare Network Interconnect (CNI), Cloudflare Tunnel, or Cloudflare Mesh.

Why are requests timing out when reaching my private origin?

The most common cause of timeouts is a missing return route on the origin's network. Ensure your routers are configured to route return traffic for Cloudflare's source ranges (100.64.0.0/12 for IPv4 and 2606:4700:cf1:5000::/64 for IPv6) back through your Cloudflare One connection.

What Cloudflare features are currently not supported for private origins?

Current limitations include lack of support for Argo Smart Routing and Dedicated CDN Egress IPs. Additionally, origin health checks require Cloudflare Load Balancing.

Primary reference: Review the original announcement for exact release details. This article is an independent explanation and does not reproduce the source text.