Peering policy

Requirements for peering

AS216212 maintains an open peering policy without specific requirements for peering. We however strongly recommend networks to consider peering if:

When peering with AS216212 we ask you to commit to the following:

If the network and AS216212 share more than one mutual IXP that sessions be provisioned at all mutual IXPs.
Configure sessions for IPv4 and IPv6 (where possible), even if the network currently only uses one of the two protocols.
Establish redundant sessions at IXPs where AS216212 maintains multiple ports for redundancy.

We will apply the following to routes inbound to AS216212:

Although AS216212 enforces strict outbound policies, we recommend peers apply similar inbound policies to our sessions.

Peers must meet the following criteria:

Maintain an up-to-date PeeringDB entry accurately reflecting the network's points of interconnection, prefix limits, traffic ratios, geographic scope, and network type.
For networks with a cone larger than one (1), provide us with an AS set to filter on.
Have a publicly routable ASN from a Regional Internet Registry, ideally with a public routing policy published with RPSL.
Have a NOC reachable at least 12/7.

For NOC, please contact by the following means:

For peering tech., trust & safety (abuse), and traffic:

All other at:

Google Sites

Report abuse