Peering Policy
Elite maintains an open peering policy.
Elite has a strong preference for private peering.
Elite does not require a formal peering agreement but will adhere to and expects peers to also adhere to the following:
- Each peer must neither be an existing transit customer of Elite, nor a downstream customer of an Elite customer.
- Each peer must maintain sufficient backbone capacity to exchange traffic without congestion.
- Each peer must have consistent route announcements at all peering locations.
- All costs shall be equally distributed between the prospective peer and Elite. Interface/Switching costs are solely those of the respective party.
- Each interconnection must be 100Mbps or greater.
- Multiple, diverse interconnects are preferred but not mandatory.
- BGP Sessions secured using MD5 encryption are preferred but not mandatory.
- Each peer must operate a 24x7 NOC contactable by email AND telephone.
- Each peer must be able to quickly diagnose and fix any denial of service attacks routing via their network. Elite reserves the right to withdraw peering at any time without notice until such attack or other abuse is rectified.
- Each peer must not establish a static route or default route to send traffic over the interconnection for a route that is not advertised over BGP.
- Neither party shall restrict, or otherwise tamper with traffic bound to the other party.
- Each peer must not re-advertise Elite routes to any other peer, such as selling Elite routes. A separate IP Transit contract may be purchased for this purpose.
- Each peer must register AND maintain routes and peering information in an IRR, such as RIPE/RADB/PeeringDB.
- Elite reserves the right to terminate any peering at any time. 30 days notice shall be given by either party to terminate a peering agreement.
- Elite reserves the right to refuse peering with any party based on commercial and/or operational reasons.