Peering Information
All our sessions are filtered with IRR, AS-SET and RPKI ROA validation.
- 1.0 Maintain an active PeeringDB page for your network.
- 1.1 Maintain an IRR AS-MACRO that is accurate and updated.
- 1.2 You must peer over an Internet Exchange or physical connection.
- 1.3 You must provide and maintain an active network contact that can respond within 48 hours.
- 1.4 We will normally only accept peering if we do not share routes directly, for example where you are not already on the route server.
- 1.5 Inactive sessions will be decommissioned after 7 days of inactivity if there is no notice of downtime.
- 1.6 All routes sent to us must be in your AS-SET, have a valid IRR or ROA, and must not have an invalid RPKI status. Our IRR filters are updated every 24–48 hours.
- 1.7 Do not send default or static routes to us.
- 1.8 We may deny peering requests if there is low traffic from your network to ours.
- 1.9 Peering sessions must be over IPv4 and IPv6, or IPv6 only. IPv4-only public peering requests will not be accepted.
Evalse maintains the right to deny peering with networks that do not meet the criteria above.
Note: We only accept IRR records from ARIN, RIPE, APNIC, LACNIC and AFRINIC. If you do not have IRR records with these providers, you must have a valid RPKI ROA for routes to be accepted through us.
Email peering@evalse.com to request peering.