Eurasia Peering Policy

Eurasia Peering is managed neutrally with respect to carriers and ISPs and is located in carrier neutral colocation sites. It does and will not compete with its members.

It is owned by IXcellerate, a carrier neutral colocation provider, but it is managed independently and once it has sufficient members the governance will be taken over by its members.

The governance of the internet exchange will be done by IXcellerate initially but as soon as we have sufficient members a governing¬† body will be set up to ensure continuity of service for member independent of IXcellerate and to guide the exchanges’ development in Moscow and across Eurasia.

Eurasia Peering has an open peering policy as long as members meet the minimum requirements below and comply with the connection guide and Terms and Conditions.

Peering relations between Eurasia Peering members is based either on bilateral agreements reached directly between parties and using BGP routing or through usage of our public Route Server service to reach as much networks as available Eurasia Peering.

Members must be a customer of IXcellerate so a cross-connect to the exchange can be ordered and provisioned.

There are no other additional charges. Members must comply with the following policies:

  • A publicly routable ASN
  • Publicly routable address space (at least one /24)
  • ASN record completed in PeeringDB
  • 24x7 NOC contact capable of resolving BGP routing issues
  • BGP-4 (Border Gateway Protocol Version 4) - Peering between Members' routers across the IXP will be via BGP-4.
  • Sign a cross-connection agreement with IXcellerate to get access to the platform and agree with the terms and conditions
  • It is not allowed to monitor or capture the content of any other member’s data traffic which passes through the IXP
  • Eurasia Peering will monitor traffic solely to gather the data required for traffic analysis and control
  • Routing and peering¬† information must be provided by member for sharing between them
  • Member contact information must be provided to enable a response in the event of security problems, infrastructure failures, routing equipment failures, and software configuration mistakes etc.