Peering Policy


This document describes the peering policies for (AS201281).


An Internet Exchange (IX) is a location where ISPs and network operators come together to peer directly or indirectly. Most often these peerings are settlement-free. Peering enables us to provide better experience for customers by interfacing with the networks directly rather than via transit paths.

Policy Statement has an open peering policy, all networks matching the following technical requirements are welcome to peer with us.

Our preference is to setup multiple peering sessions for redundancy wherever and whenever possible. will also peer with route servers on all IXs where we are present. In general, peering sessions with AS201281 will advertise all AS201281:AS-MAZOYER-EU (in RIPE IRR database) routes.

Peering Requirements (General)
  • To be eligible for peering, each candidate must:
    • Use a registered public autonomous system (AS) number;
    • Publish valid contact information via PeeringDB; and
    • Maintain valid AS and prefix records with a public Internet Routing Registry (IRR).
  • A peer may only send toward us traffic intended for a destination network we advertise. The use of static or default routes toward us is not permitted.
  • Peers must ensure that their policies in PeeringDB (e.g. maximum prefix count) are kept accurate.
  • The following features are encouraged but not required:

AS201281 will review it's peering policy quarterly and reserves the right to modify this policy at any time. We may also filter any routes which we determine should not be advertised to over the agreed upon peering session. We will by default filter any bogon prefixes (i.e. IP space allocated by RFCs 1918, 5735, and 6598) and default routes.


Report Abuse—Reports of abusive activity originating from AS201281 (spam, DDoS, copyright violations, etc.)
Peering Request—Requests for new peering sessions or changes to existing sessions.
Ask Questions—All other routing/network related issues.