Open peering policy
We peer openly, and we would rather peer than not.
Network Edge maintains an open peering policy: where there is a reasonable technical benefit to either network, we want the session. Direct interconnection shortens the path for both sides, and that is worth more to us than a selective policy would be.
We peer with regional ISPs, hosting and cloud providers, content and streaming networks, infrastructure operators and larger carriers alike.
Peering decisions remain subject to technical compatibility, available capacity, routing security and network operational requirements.
Send a peering requestOur published policy does not require
- Presence at multiple common locations
- Minimum traffic ratios
- Mandatory peering contracts
What we do care about
- Technical compatibility
- Available capacity at the exchange
- Routing security and filterable policy
- Normal network operational requirements
Where we peer
AS7201 exchange-point presence.
We continue to expand our interconnection footprint as opportunities become available. If you are somewhere we are not yet present, tell us anyway — it informs where we build next.
| Exchange | Full name | Location |
|---|---|---|
| DET-IX | Detroit Internet Exchange | Detroit / Southfield, Michigan |
| GRR-IX | Grand Rapids Internet Exchange | Grand Rapids, Michigan |
| KCIX | Kansas City Internet Exchange | Kansas City, Missouri |
| STLIX | Saint Louis Internet Exchange | St. Louis, Missouri |
| SpringIX | Springfield Internet Exchange | Springfield, Missouri |
| HOUIX | Houston Internet Exchange | Houston, Texas |
| SIX | Seattle Internet Exchange | Seattle, Washington |
Session details
| ASN | AS7201 |
| Address families | IPv4 and IPv6 |
| Peering type | Settlement-free, public and private |
| Route validation | RPKI / ROA and IRR based |
| Peering contact | Contact details |
| NOC contact | Contact details |
Technical expectations
Keep your objects current and this stays easy.
We build prefix filters from published routing policy. Registered IRR route objects, an accurate AS-set and valid ROAs are what make a session come up quickly and stay stable.
- Announce a consistent prefix set matching your IRR objects
- Maintain valid ROAs for the prefixes you originate
- Set a sensible maximum-prefix limit in both directions
- Do not point a default route at a peering session
- Keep your NOC contact reachable and current
- Tell us before large changes to what you announce
Request a session
What to send us.
- Your ASN and organization name
- Exchange point(s) where you are present
- Your IPv4 and IPv6 peering addresses
- Your AS-set and IRR objects
- Approximate prefix counts and maximum-prefix values
- NOC contact address and escalation path
Questions
Frequently asked
Do you require a minimum traffic ratio?
No. We do not enforce traffic ratios as a condition of peering.
Do I have to meet you in multiple locations?
No. A single common exchange point is enough.
Is there a peering contract to sign?
No mandatory contract is required for settlement-free peering.
How do I request a session?
Send a peering request through the contact form with your ASN, the exchange or exchanges where you are present, your IPv4 and IPv6 peering addresses, your AS-set or IRR objects, and your maximum-prefix expectations.
Do you validate what I announce?
Yes. We build filters from published IRR objects and AS-sets and apply RPKI/ROA-based route origin validation. Keeping your objects current is the fastest way to keep a session healthy.