Peering Policy


Amusnet Interactive uses PeeringDB as a single authoritative source of truth. That means peering partners must have an up-to-date PeeringDB entry before the bi-lateral peering session establishment.

Amusnet Interactive will use industry standards to secure the peering sessions. That includes industry-standard practices and best practices, including but not limited to BCP-38 and route filtering.

Both parties should have a good set-up route-set or AS-SET, up-to-date prefix maximums defined in PeeringDB. Amusnet Interactive will use this data to filter routes received from the network’s BGP sessions.

Both parties must have an up-to-date NOC contact email, which is responsive to raised issues and concerns.

Basic requirements

Those who request private peering with Amusnet Interactive should:

• Not to announce routes received from other peers or upstreams.

• Not announce martian routes or the default route (

• Manage 24×7 Network Support Team.

• Provide an escalation matrix upon request – to quickly resolve possible network issues.

Private Interconnection (PNI) Requirements

If the Operator maintains more than 500 players, it can request a PNI. We accept single or multiples of 1G or 10G connections.

Peering partners will assume financial and all other responsibilities for the connections.

Important Notices

To ensure the quality of operations, we reserve the following rights under our Peering Policy:

  1. To alter our peering policy and peering requirements at any time.
  2. To accept or decline a peering request at any time for any reason.
  3. To suspend peering connectivity without notice in the event of:
    • – degraded severe quality
    • – high latency, packet loss, or jitter pattern is detected
  4. To take appropriate traffic engineering steps to maintain service quality.
  5. To selectively withdraw prefixes as needed to protect service quality.
  6. To terminate any peering connection at any time without notice.

Peering partners will assume financial and all other responsibilities for the connections.

Details on PeeringDB: