PEERING POLICY

Peering Requests

Peering requests must be submitted to Angani via email. Angani reserves the right to accept or reject a peering request in its sole discretion and may but has no obligation to explain the basis for its decision.

Technical Requirements

• A publicly routable and visible unique ASN
• Network edge router capable of running BGP
• BGP session authentication as mutually agreed
• Complete and updated PeeringDB entry and profile
• 24/7 NOC Contact provided at the time of session establishment
• Peering partner must adhere to the technical requirements of each applicable Internet Exchange/Data center.
• When feasible, Angani prefers to have bi-lateral sessions configured across all common Internet Exchanges, with networks we serve traffic to.
• A cross-connect to Angani at the desired POP that Angani has a presence in, for private peering.

General Terms

Each party bears its own expenses of reaching the peering site and responsibility for any necessary licenses, authorizations or other regulatory approvals.

Angani may suspend or terminate connectivity with the peering partner at any time with or without notice.

Peering partner will make every effort to avoid malicious, illegal, or other undesirable content on its network.

Angani reserves the right to modify this peering policy and its requirements at any time.

These policies operate solely as guidelines and neither this policy nor the act of peering create any binding obligations, or promises by Angani in connection with network performance, peering arrangements or otherwise.