Our policies for Settlement-Free Interconnections - Peering
This document shall serve as a guideline for Internet Service Providers seeking Settlement-Free Interconnection (SFI), also known as Peering, with Pacific Internet Exchange, LLC.
Pacific internet Exchange (PIE) is focused on providing excellent support and bandwidth to customers that focus on Asia. Our location in San Francisco, CA provides us with a central location and the ability to grow for the future. Our current bandwidth usage is over 2 Gb/second. This is carried by various transit and peering agreements.
We recognize that the volume of our traffic is growing rapidly and that this affects many regional carriers in Asia causing unequal transit fees to be placed on them by larger "upstream" carriers. PIE is willing to consider any peering agreement that is mutually beneficial to the parties involved. Our 385 Gb/second quad redundant network backplane give us room for both large and small customers to grow and be free from congestion that can be caused from oversold bandwidth.
We are strategically positioned to be able to connect with all major US and Asian carriers, and have an open peering policy with all providers provided the exchange is mutually equitable and cost effective. Regional Asian ISPs that currently have a presence at PAIX may be able to save substantial amounts of money, because PAIX also has a virtual presence less then 25 meters from their Datacenter at our Datacenter in San Francisco.
Despite PIE not being a Tier 1 operation, we have outgoing traffic volume greater than many of today's Tier 1 operators due to better pricing and superior service. This being the case it may make financial sense to peer and bring the outgoing traffic from PIE directly to your network over any unused resources already provisioned to you. For these reasons PIE must exempt itself from in/out ratio calculations. Most Asian operators will have a cost savings from a peering agreement with PIE. American and European operators may not see a direct savings, but indirectly through creative routing tables and private agreements PIE is willing to facilitate and forward inbound and outbound traffic to regional providers in America and Asia. |
|
 1. Operations Requirements
| 1.1 |
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.2 |
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 engineer to trace ongoing network attacks within a reasonable amount of time. |
| 1.3 |
Both parties shall provide access to a route server, looking glass, or similar service for the purposes of routing audits, diagnostics, and troubleshooting. |
2. Technical Requirements
| 2.1 |
Both parties shall maintain sufficient backbone and interconnection capacity to support the traffic being exchanged. Both parties shall work quickly to establish additional capacity to accommodate traffic growth if needed or desired. |
| 2.2 |
Both parties are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purposes of filtering. Both parties shall make good faith efforts to keep this information up to date. |
| 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 establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP or similar. Neither party shall alter, sell, or give next-hop to a third party. These activities are considered theft of service, and will be prosecuted to the fullest extent of the law. |
| 2.6 |
Neither party shall announce to the other a more specific route of a prefix heard from a third party transit customer. |
| 2.7 |
Under no circumstances shall the interconnection partner be a simultaneous peer and transit customer. |
3. Peers
| 3.1 |
A peer will receive all Peering traffic and routes originating within the PIE's Autonomous System. Both parties will be expected to announce a consistent routing view across all interconnection points. |
| 3.2 |
A peer may, at PIE's discretion, receive only Peering traffic and routes originating from customers in the specific geographic region or from PIE`s transit customners where the interconnection takes place. This is done to facilitate the exchange of local traffic with regional providers who might not have settlement free Peering. |
4. Peer Requirements
|
|
| 4.1 |
At least 20Mb/s of aggregate traffic to exchange. |
| 4.2 |
Each interconnection shall have no less than 100Mb/s of capacity. |
5. General Policy
| 5.1 |
This policy may be updated from time to time, as market and traffic conditions affecting network interconnections change. PIE reserves the right to modify this policy at any time. |
| 5.2 |
In the event of a severe, criminal, or quality-of-service impacting violation of these policies, the interconnection may be temporarily suspended without notice. |
| 5.3 |
Any interconnection may be terminated for any reason, with 30 days notice. |
| 5.4 |
All requirements must be met at the time the request for Peering is made, and must continue to be met for the duration of the interconnection. |
| 5.5 |
PIE reserves the right to accept or decline any interconnection request for any reason. |
| 5.6 |
The necessary provisioning of local loop and all costs associated with it are the responsibility of the party that wishes to peer with PIE.
|
| 5.7 |
All equipment maintenance and troubleshooting is the responsibility of the peering partner that has requested the connection.
|
| 5.8 |
PIE will not charge port fees at this time. Depending on future port availability and costs in the future port fees may be levied.
|
|
