diff --git a/src/content/docs/aegis/about/ips-allocation.mdx b/src/content/docs/aegis/about/ips-allocation.mdx
index 51b41a191524173..ad833699160b570 100644
--- a/src/content/docs/aegis/about/ips-allocation.mdx
+++ b/src/content/docs/aegis/about/ips-allocation.mdx
@@ -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
diff --git a/src/content/docs/aegis/about/reuse-and-coalescing.mdx b/src/content/docs/aegis/about/reuse-and-coalescing.mdx
new file mode 100644
index 000000000000000..1e05f3d8553308e
--- /dev/null
+++ b/src/content/docs/aegis/about/reuse-and-coalescing.mdx
@@ -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.
\ No newline at end of file