Peering Policy
This document serves as a guideline for Internet Service Providers seeking Settlement-Free Interconnection, also known as Peering, with Internap Network Services Corporation ("Internap"). All questions regarding this document, or requests for Peering, should be directed to peering@internap.com
| 1. Operations Requirements | |
| 1.1 | Both parties shall maintain a fully staffed Network Operations Center that operates and is reachable via phone and e-mail 24 hours a day, 7 days a week. |
| 1.2 | Both parties shall provide an escalation path for resolving network issues in a timely fashion. Issues of a non-emergency technical nature should be responded to within 48 hours. |
| 1.3 | Both parties shall make every reasonable effort to provide advance notice of any planned maintenance, and immediate notice of any unplanned outages, affecting any interconnection. |
| 1.4 | Both parties shall be responsive to unsolicited bulk email, hacking, Denial of Service, and other network security and abuse issues. A good faith effort should be made to provide a qualified network engineer to trace ongoing network attacks within a reasonable amount of time. |
| 1.5 | The interconnection partner must not currently be or have been an IP transit customer of Internap in the recent past. |
2. Technical Requirements | |
| 2.1 | Both parties shall maintain a redundant backbone network with sufficient capacity to minimize queueing and ensure delivery of traffic both during normal and single-failure scenarios. Both parties shall act quickly and diligently to establish additional capacity to proactively accommodate traffic growth. |
| 2.2 | Both parties shall announce consistent routes across all interconnection points. |
| 2.3 | Both parties shall make every reasonable effort to restrict the transmission of Denial of Service attacks and packets with forged source addresses from their network. |
| 2.4 | Both parties shall announce only their own routes and the routes of their transit customers to the other party. No other routes are permitted, and may be filtered if detected. |
| 2.5 | Neither party shall abuse the peering relationship in any way. Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP. Neither party shall alter, sell, or give next-hops to a third party. Neither party shall use the other party's network for transit, or engage in any other routing manipulation that causes the other party's network to provide transit to peers. This would include, but is not limited to, establishing a tunnel between two different peering interconnection points, or announcing to the other the more specific routes of prefixes learned via a third party mutual transit customer. |
| 3. Interconnection Requirements - North American Region | |
| 3.1 | General Interconnection Requirements |
| 3.1.a | For all interconnect types (Public and Private), interconnection must occur at a minimum of two (2) diverse peering points. For US peers, those interconnections must come from at least two (2) different geographic regions: East, Central, and West. Specific exemptions on the number of locations may be made, at Internap's discretion, for networks that operate in regions where Internap does not currently interconnect with other networks. |
| 3.2 | Public Interconnection Requirements |
| 3.2.a | At least 5 Mbps of aggregate traffic, measured using 95th Percentile in either direction, must be exchanged on an ongoing basis. Specific exemptions on traffic levels may be made, at Internap's discretion. |
| 3.2.b | Both parties shall have sufficient capacity into the exchange switch to pass all traffic sent and received without queueing or loss. Both parties shall work proactively and diligently to establish additional capacity to accommodate traffic growth. |
| 3.3 | Private Interconnection Requirements |
| 3.3.a | At least 50 Mbps of aggregate traffic, measured using 95th Percentile in either direction, must be exchanged on an ongoing basis. Specific exemptions on traffic levels may be made, at Internap's discretion. |
| 3.3.b | Each interconnection shall have no less than 1 Gbps of capacity. |
| 4. General Policy | |
| 4.1 | This policy may be updated from time to time, and Internap reserves the right to modify, replace, or nullify this policy at any time. |
| 4.2 | Interconnection partner agrees to be bound at all times by Internap's™ current Acceptable Use Policy, as of the Effective Date and all subsequent versions that may be modified from time to time, which is incorporated herein by this reference and is maintained at the following URL: http://www.internap.com/legal/acceptable-use-policy.html |
| 4.3 | Any interconnection may be temporarily suspended or disconnected at the sole discretion of either party. |
| 4.4 | Any interconnection may be terminated for any reason, with 30 days notice to the other party. |
| 4.5 | Internap reserves the right to accept or decline any interconnection request for any reason. |