Locking down origin access with dedicated egress addresses
Firewall allowlisting remains one of the most basic ways to restrict traffic to an origin server. Cloudflare has long published its IP address ranges so customers can permit only Cloudflare traffic at their layer 3 firewall. But those ranges are shared across many Cloudflare services and customers, so allowlisting the whole list does not always deliver the isolation a security team wants. Aegis, launched in March 2023, was built as an intermediary answer: Cloudflare gives you a dedicated IP address or set of addresses to egress from, and you allowlist only those. The service now adds Bring Your Own IPs (BYOIP) support, a public Aegis API, and a gradual rollout of IP utilization observability.
How Aegis differs from the default egress path
Without Aegis, egress traffic uses Cloudflare's publicly listed IP ranges, which are scattered across the network, so traffic to a customer origin can leave from many servers.

Aegis addresses are not necessarily present on every server, at least for IPv4. Requests must therefore be steered through Cloudflare's network to a machine holding the Aegis address before they can leave toward the origin.

Routing mechanics: soft-unicast and Unimog
Dedicated Aegis IPs live in a set of data centers that the customer picks together with Cloudflare, ideally close to the origin for both security and performance. Aegis uses soft-unicasting to share a /32 IPv4 egress address across many servers, so one subnet can span multiple data centers. Return traffic from the origin heads to the nearest data center, where Cloudflare's L4, XDP-based load balancer, Unimog, routes the packets back to the machine that opened the original connections.
The result is local, fast egress: Anycast at the BGP layer, then an IP-and-port range to pick a specific machine in the right data center. Cloudflare's broader egress range covers all data centers and machines, but an Aegis customer's handful of IPv4 addresses confines egress to a few data centers.

IPv4, capacity, and what the IP count buys you
Each Aegis customer receives two /64 prefixes for IPv6, globally allocated and announced. Outside the China Network, every Cloudflare data center then has hundreds or thousands of addresses available to egress traffic directly — essentially eliminating capacity as a concern.
IPv4 is more constrained and more expensive, so the number of addresses is tailored per customer during onboarding. IPv4 also narrows egress: only a fraction of data centers will announce your addresses, making the use of a small number of egress IPs a potential bottleneck, though careful provisioning mitigates it. BYOIP for Aegis lets you onboard an entire IPv4 /24 prefix or an IPv6 /64 for higher capacity at lower cost.
At launch, each Aegis IP was allocated to one data center, so at least two IPv4 addresses were needed for resiliency. That was later expanded so a single address can be announced from up to four data centers by slicing the port range into four subsets, one per facility — fewer entries in your layer 3 allowlist and lower leasing cost.
Recall how a request travels: an ingress data center near the eyeball accepts it, then BGP (or Argo Smart Routing, if enabled) carries it to an egress data center near the origin. Under Aegis the possible exit points are only the data centers announcing your Aegis IPs, because addresses are placed near your origins, the egress data center and the Aegis-enabled data center are usually one and the same. Changing optimal routes mean this cannot be guaranteed every time, which is why IPv6 is the recommended choice: it preserves the full spread of Anycast egress points.

Why port count bounds concurrency
An IP address has 65,535 ports, and a request egresses from one port on the Aegis address to one port on the origin address. A TCP connection is identified by a 4-way tuple — source IP, source port, destination IP, destination port. UDP may use a connected 4-way tuple or an unconnected 2-way one (bind IP and port). Aegis carries both protocols, and both depend on IP:port pairings. A single source port can hold multiple connections only if the destination ip:port differs.
Normally Cloudflare's egress addresses connect to many destination IPs and ports, but Aegis concentrates all traffic onto the same (or a few) origin address(es) from the same (or a few) source address(es). That is what creates the capacity limit. Between one client and one server, the ceiling is 65,535 concurrent connections, and port-range assignments across servers plus imperfect load distribution usually push the practical number lower. Cloudflare plans around roughly 80% of IP capacity to absorb spikes; exhausting the ports means new connections are dropped. For that reason the planning figure is 40,000 concurrent connections per Aegis IP address per origin.
Aegis IPv4 | Aegis IPv6 | |
|---|---|---|
Physical points of egress | 4 physical data center sites (1-2 cities near origin) per IP address | All 300+ Cloudflare locations (excluding China network) |
Capacity | One IPv4 address per 40,000 concurrent connections per origin | Two /64 prefixes for all Aegis customers (>36 quintillion IP addresses)~50,000x capacity of IPv4 config |
Pricing model | Monthly fee based on IPv4 leases or BYOIP for Aegis prefix fees | Included with product purchase or BYOIP for Aegis prefix fees |
Connection reuse keeps origin load down
Early protocols tied requests to connections 1:1. HTTP/1.1 allowed connection reuse, so requests sharing the same source ip:port and destination IP:port travel over one connection — meaningful for a modern page that fires hundreds of requests at load time. HTTP/2 added connection coalescing, which can merge requests for different domains into one connection when they target the same destination IP and the server certificate is authoritative for both. The volume of reuse and coalescing depends heavily on traffic patterns, so the theoretical worst case is a 1:1 connection-to-request ratio — in practice almost never seen. Allocations are sized conservatively to match.
Pushing traffic through fewer source addresses also lowers the origin's cost: fewer connections to open, less CPU and memory tied up handling inbound requests, and reduced latency. Security benefits too, since open connection access is more restricted.
What's new and recommended configurations
Three capabilities are now available or rolling out:
- Public Aegis API
- BYOIP for Aegis
- Customer-facing Aegis observability, coming soon via gradual rollout
For customers leasing Cloudflare-owned addresses, the API enables and disables Aegis on zones in the parent account that owns the lease; multiple-account deployments still need Cloudflare's account team. For BYOIP, the API covers the parent account and any accounts holding delegated prefix permissions.
Observability will let every Aegis data center compute and report usage per origin IP:port at regular intervals. The data lands in an internal database and is exposed through the GraphQL Analytics API, with aggregations such as averages over time or summed totals. That gives customers port-usage tracking by IP, account, zone and data center, and RSS-based notifications with thresholds of their own design — letting them manage deployments and flag changes to Cloudflare rather than the reverse.
BYOIP | Cloudflare-owned IPs | |
|---|---|---|
Enable Aegis on zones on parent account | ✓ | ✓ |
Enable Aegis on zones beyond parent account | ✓ | ✗ |
Disable Aegis on zones on parent account | ✓ | ✓ |
Disable Aegis on zones beyond parent account | ✓ | ✗ |
Access Aegis analytics via the API | ✓ | ✓ |
Cloudflare also points to adjacent practices:
- IPv6 on the origin: where supported, it yields better resiliency, performance and availability at lower cost.
- HTTP/2 or HTTP/3: both enable reuse and coalescing, cutting origin load and request latency.
- Layered protection: pair Aegis with Access and CNI, Authenticated Origin Pulls, or other Cloudflare products to verify and protect traffic end to end.
Key sizing takeaways: concurrent connections can be as high as 1:1 with concurrent requests, each Aegis IP supports an estimated 40,000 concurrent connections per origin IP, and Cloudflare derives that guidance from the 40,000-connection figure to limit overload risk.



