Terms & Conditions - StarHub’s IP Peering Policy
- Peering is a commercially-negotiated and settlement-free agreement between operators to facilitate direct and mutual exchange of Internet traffic. Peers are typically operators of similar network size and will exchange approximately equal volumes of traffic to ensure mutual benefits accrue to both peers.
- StarHub Ltd (“StarHub”) is willing to consider selectively peering with other Internet backbone providers and Internet Service Providers when such peering agreements provide significant benefits to StarHub and its customers. As peering agreements are based on a mutual exchange of value, operators that do not operate extensive Internet backbones will not typically qualify for peering agreements with StarHub. The exchange of traffic with other operators, such as content providers and Content Delivery Networks, generally take place through other forms of commercial agreements.
- This Peering Policy describes guidelines used to evaluate all requests for peering agreements. The Peering Policy is subject to periodic review to ensure that it continues to meet StarHub’s business needs. We may modify this Peering Policy at any time, and such modifications will be updated on this page. Meeting some or all of the requirements set-out \herein does not guarantee that StarHub will enter into a peering agreement with any particular operator. StarHub reserves the right to establish, maintain, and discontinue peering agreements in its sole discretion.
- Information for Potential Peering Partners:
- The StarHub IP network consists of several Autonomous System Numbers (“ASNs”). StarHub makes available AS4657 and AS38861 for selective peering in Singapore, Hong Kong, the United States and parts of Europe. More technical information on the StarHub network can be found at: https://www.peeringdb.com/net/1062.
- Any requests to peer with StarHub will be reviewed on an individualised basis. Any potential peering partner should submit its request to StarHub at the following email address: firstname.lastname@example.org.
- To assist in StarHub’s review, the potential peering partner’s request should minimally include the following information:
- The locations and exchange points in which the operator seeks to peer with StarHub;
- A list of the operator’s ASNs and prefixes served;
- A description of the type of traffic which the operator provides over its network; and
- Information showing that the operator meets the “Peering Qualification Guidelines” set-out in the following section.
- StarHub strives to contact potential peering partners within a reasonable timeframe after receipt of their applications. Please note that any existing customers taking IP services for AS4657 and AS38861 cannot simultaneously be a peering partner.
- Peering Qualification Guidelines:
- The traffic to and from AS4657 and AS38861 must be On-Net only, and should average at least 1Gbps to and from StarHub during the busiest hour of the month;
- To ensure a reasonable quality of service, peering partners should maintain a fully functional 24x7 Network Operations Centre, and agree to exchange escalation contacts with StarHub.
- The peering partner must agree to rectify any issues highlighted by StarHub within a reasonable timeframe. The peering partner should also agree to cooperate with StarHub to resolve operational and network abuse issues, and to deal with any potential security incidents (such as distributed denial of service attacks);
- The peering partner must agree and comply with the following routing policies:
- At each exchange point, the peering partner must: (1) use the same peering ASN(s); and (2) announce a consistent set of routes, unless otherwise mutually-agreed with StarHub;
- All routes exchanges must be from the peering partner and its customers only. No transit or third-party routes should be announced;
- The peering partner must filter route announcements from its customers by prefix; and
- Both parties agree not to abuse the peering agreement through activities such as (but not limited to): (1) pointing a default route at the other, or forwarding traffic for destinations not clearly advertised; (2) selling or providing the next-hop to third parties; or (3) resetting the next-hop; and
- The peering partner should be financially stable.
- Ongoing Requirements for Peering Agreements:
All peering agreements are subject to ongoing review to ensure that peers continue to meet the Peering Qualification Guidelines set out above. To ensure continued mutual benefits to both parties, peers should maintain a balanced traffic exchange ratio with StarHub that is no more than 2:1 (traffic out: traffic in) on average each month. For traffic management purposes, peers should also have a reasonably low peak-to-average ratio. Any peers whose traffic exchange ratio rises above 2:1 will be requested to take actions to balance the costs of transport.
StarHub does not guarantee that it will enter into a peering agreement with any potential peering partner which meets the Peering Qualification Guidelines. We will evaluate each application on a case-by-case basis, taking into consideration all relevant business and commercial factors. StarHub reserves all rights to decline to enter into a peering agreement with all potential peering partners.