Peering Policy

AS215207

We do not have any prerequisites for peers regarding network size, minimum locations, etc. We only have the following requirements:

1. IPv6: Your network must be fully capable of passing IPv6 traffic.
2. PeeringDB: You must have an updated PeeringDB page that reflects the current state of your network, including all PoPs, IXPs, and NOC contact information.
3. Common Locations: We must be able to peer at all common Internet Exchange Points. If you peer with route servers at these locations, we consider this requirement satisfied. However, we may reach out to request direct peering for routing optimization or other reasons. If you would like to arrange direct peering over an IXP, please do not hesitate to reach out. We love peering!
4. Routing Security: You must have RPKI ROAs for all prefixes you announce. You must not leak routes or advertise invalid routes. Please do not point
5. Settlement-free Peering: We will not peer with networks that require payment for peering; in turn, we do not require payment for peering. This rule excludes transit providers who we specifically negotiate with.
6. Best-effort SLAs: As Aethernet is a hobbynet, we do not guarantee minimum uptime or performance. If you encounter these types of problems, our NOC can respond to email within 48 hours at most. We also have a NOC phone number listed as well but request that you only use that if our network is threatening the stability of other networks. Contact details can be found on PeeringDB.