Skip to content

[Aegis] Connection reuse and coalescence #23804

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 21, 2025
Merged

[Aegis] Connection reuse and coalescence #23804

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fa7616d
Create new page and cross-link from ips-allocation
RebeccaTamachiro Jul 18, 2025
2acbfa5
Add Example placeholders under each concept and link to blog
RebeccaTamachiro Jul 18, 2025
d22d298
Fill in example placeholders
RebeccaTamachiro Jul 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/content/docs/aegis/about/ips-allocation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,8 @@ Refer to [connection forwarding](/aegis/about/connection-forwarding/) to underst

<Render file="concurrent-connections-explainer" />

Aegis also benefits from [connection reuse and connection coalescing](/aegis/about/reuse-and-coalescing/).

[GraphQL Analytics API](/aegis/analytics/) allows you to get visibility over Aegis IP utilization.

## Regional services
Expand Down
27 changes: 27 additions & 0 deletions src/content/docs/aegis/about/reuse-and-coalescing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
title: Connection reuse and coalescing
pcx_content_type: concept
sidebar:
order: 4
label: Reuse and coalescing
---

import { Details } from "~/components";

Aside from [concurrent connections](/aegis/about/ips-allocation/#connections-to-your-origin)[^1], connection reuse and connection coalescing are also important concepts. They both have impact on latency and are considered when allocating your Aegis IPv4 addresses.

Implemented by HTTP/1.1, connection reuse describes multiple requests passing through one same connection (between one source IP:port and one destination IP:port). It is commonly the case even for simple websites nowadays.

<Details header="Example">
When a connection is initiated for `shop.example.com`, several embedded subresources may be requested - CSS, image files, advertisement, etc. This can mean hundreds of requests just for the website to load. Instead of having a one to one ratio of request per connection, a single connection is used for multiple requests.
</Details>

With HTTP/2, requests can use the same connection even if they are for different domains.

<Details header="Example">
A connection initiated for `shop.example.com` can be used for requests for `blog.example.com` as well - as long as the requests have the same destination IP:port and the server TLS certificate is authoritative for both hostnames.
</Details>

Refer to the [Cloudflare blog post](https://blog.cloudflare.com/aegis-deep-dive/) for further details.

[^1]: If you have one Aegis IP and two origins (A and B), this single Aegis IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B.