Techniq World
Software

Cloudflare Rolls Out Application Services for Private Origins

Cloudflare has made Application Services for Private Origins generally available as of November 15, 2026. The release enables public HTTP and HTTPS traffic to proxy from...

In brief

Cloudflare has made Application Services for Private Origins generally available as of November 15, 2026. The release enables public HTTP and HTTPS traffic to proxy from...

Public traffic can now reach applications hosted on private networks without exposing IP addresses or opening inbound firewall ports, following a general availability release on November 15, 2026.

Routing Public Traffic to Private Infrastructure

Cloudflare has made Application Services for Private Origins generally available as of November 15, 2026. The release enables public HTTP and HTTPS traffic to proxy from public hostnames directly to origins residing within private networks. Developers and network administrators can route this traffic over existing Cloudflare One connectivity options, which include Cloudflare WAN—utilizing IPsec, GRE, or CNI—as well as Cloudflare Tunnel and Cloudflare Mesh.

Once traffic reaches the origin through these designated connectivity types, standard Cloudflare features apply identically to how they handle traffic destined for public origins. These integrated proxy features include the content delivery network (CDN), Web Application Firewall (WAF), and caching capabilities.

Confirmed Network Specifications and Setup Requirements

Authoritative specifications confirm that deployment requires specific network routing configurations and account-level provisioning. Return routes must be established within the private network for Cloudflare source IP ranges, utilizing 100.64.0.0/12 for IPv4 (which is set as default and remains configurable) and 2606:4700:cf1:5000::/64 for IPv6.

Account access requires explicit enablement, as Private Origins must be activated for the specific account through an account team contact. Additional technical prerequisites include establishing a route to the origin within the default virtual network and configuring a DNS record with private network routing enabled.

Conversely, certain capabilities remain unsupported at launch. Private-to-private connectivity is not yet supported by the platform. Any deployment details, pricing models, or expansion timelines not explicitly covered in the official documentation remain unconfirmed.

Next Steps for Network Administrators

Teams looking to implement the feature must verify prerequisites and follow the setup guide specific to their chosen Cloudflare One connectivity type. Administrators should contact their account team to ensure Private Origins is enabled for their account, configure the necessary IPv4 and IPv6 return routes, and create a DNS record with private network routing enabled.

Frequently Asked Questions

Q1: When did Cloudflare make Private Origins generally available?

The service became generally available on November 15, 2026.

Q2: What traffic types and connectivity methods are supported?

The service proxies HTTP and HTTPS traffic from public hostnames to private network origins using Cloudflare WAN (IPsec, GRE, or CNI), Cloudflare Tunnel, or Cloudflare Mesh.

Q3: Is private-to-private connectivity supported?

No, private-to-private connectivity is not yet supported.

Leave a Reply