Peering Policy Tracker
This tracker provides an overview of members with specific peering policies, so CNX participants can understand which peers are available via route servers (RS) and which require bilateral sessions. {:.mt-5 .mb-3}
Current CDN Policies at CNX
{: .mt-4 .mb-2}
| Network | ASN | RS Usage | Notes |
|---|---|---|---|
| ACE CDN | 139341 | Prefers bilateral | Operates a peering portal and invites members to set up direct sessions. |
| Tencent | 132203 | Selective | Policy states peering may depend on technical, commercial, or legal requirements; bilateral often preferred. |
| {: .table .table-striped .table-bordered .table-sm .align-middle} |
Guidance for Members
{: .mt-4 .mb-2}
- Always start with the CNX route servers for general reachability.
- If you have significant traffic with a CDN that requires bilateral, reach out directly or through CNX for an introduction.
- Keep PeeringDB entries up to date so CDNs can quickly validate your details.
Updates
{: .mt-4 .mb-2} This tracker will be updated as CDN members change their peering policies. If you notice differences between this list and a CDN’s published policy (e.g. on PeeringDB), please let us know at Email protected. {:.mt-5 .mb-3}