Skip to content

LSHIY Network Peering

LSHIY has an open peering policy, subject to certain technical, commercial and legal requirements.

We're able to peer at the internet exchanges (IXPs) and private facilities listed in our PeeringDB entry. Note that some interconnect locations may not be available for all networks.

Peering Benefits

Economic

LSHIY offers peering on a non-charged ("settlement free") basis. As a result, networks may find that peering reduces their overall costs compared with exchanging traffic with LSHIY via their upstream transit providers. Note that peering occurs at common physical locations and both LSHIY and any peering network bear their own costs in reaching any such location. All of LSHIY’s peering locations are in its PeeringDB entry.

Control

A peering relationship with LSHIY removes intermediate network operators (ASNs) from the traffic path. This brings greater control in the form of path preferences and in capacity management for LSHIY traffic. Resolving operational issues may also be made easier without intermediate network operators in the traffic path.

Prerequisites to Peer with LSHIY

Before submitting a peering request, your network must have:

  • Publicly routable ASN

  • Publicly routable address space (at least one /24 of IPv4 and/or one /48 of IPv6 space)

  • ASN record completed in PeeringDB

  • 24x7 NOC contact

  • Presence at one or more internet exchanges or private peering interconnection facilities listed for LSHIY in PeeringDB

  • Up to date Maintainer, ASN, AS-SET, and Route/Route6 objects in an internet routing registry (IRR) used by LSHIY.

Private and Public Peering Explained

Private Peering

Private peering allows a network to connect directly with LSHIY over a dedicated physical link known as a private network interconnect (PNI).

Public Peering

Public peering allows a network to connect with LSHIY and other networks over a shared fabric known as an internet exchange (IX). Peering with other networks is achieved by first physically connecting to an IX and then creating Border Gateway Protocol (BGP) sessions with other networks also physically connected to the IX.

LSHIY ASNs

LSHIY manages several ASNs that you may be able to peer with or see our traffic originating from.

Peering ASNs AS955 is the primary peering ASN for LSHIY.

Non-Peering ASNs AS321687: The IP addresses under this ASN are in use by LSHIY customers. (Including BYOIP, cloud platform, guest network and internet service.)

Local Preference

When multiple routes are available, BGP will prioritize the route with the highest local preference.

Type LocalPref
Downstream 400
Private Peer 300
Public Peer 200
Upstream 100

BGP Community

LSHIY will use reasonable efforts to honor the preferences indicated, but may discard any of this information if it conflicts with a higher-priority policy on the LSHIY network.

When multiple Action Communities are used, the policy will be executed according to the priority. The larger the number, the higher the priority.

| Action                                   | Community | Large Community | Priority |
| ---------------------------------------- | --------- | --------------- | -------- |
| Prepend 1x to all AS’s                   | 955:1     |                 | 810      |
| Prepend 2x to all AS’s                   | 955:2     |                 | 820      |
| Prepend 3x to all AS’s                   | 955:3     |                 | 830      |
| Prepend 4x to all AS’s                   | 955:4     |                 | 840      |
| Prepend 5x to all AS’s                   | 955:5     |                 | 850      |
| Prepend 1x to specific AS                |           | 955:1:peer-as   | 710      |
| Prepend 2x to specific AS                |           | 955:2:peer-as   | 720      |
| Prepend 3x to specific AS                |           | 955:3:peer-as   | 730      |
| Prepend 4x to specific AS                |           | 955:4:peer-as   | 740      |
| Prepend 5x to specific AS                |           | 955:5:peer-as   | 750      |
| Do not announce to all AS’s              | 955:100   |                 | 600      |
| Do not announce to all Upstream AS’s     | 955:101   |                 | 300      |
| Do not announce to all Public Peer AS’s  | 955:102   |                 | 300      |
| Do not announce to all Private Peer AS’s | 955:103   |                 | 300      |
| Do not announce to all Downstream AS’s   | 955:104   |                 | 300      |
| Do not announce to specific AS           |           | 955:199:peer-as | 500      |
| Announce to all Upstream AS’s            | 955:201   |                 | 200      |
| Announce to all Public Peer AS’s         | 955:202   |                 | 200      |
| Announce to all Private Peer AS’s        | 955:203   |                 | 200      |
| Announce to all Downstream AS’s          | 955:204   |                 | 200      |
| Announce to specific AS                  |           | 955:299:peer-as | 400      |
| Export blackhole to all AS’s             | 65535:666 |                 | 999      |
| Prefix type                      | Community | Large Community        |
| -------------------------------- | --------- | ---------------------- |
| Prefix learned from Upstream     | 955:1001  | 955:1001­:upstream-as   |
| Prefix learned from Public Peer  | 955:1002  | 955:1002:ixpeer-as     |
| Prefix learned from Private Peer | 955:1003  | 955:1003:peer-as       |
| Prefix learned from Downstream   | 955:1004  | 955:1004:downstream-as |
| Prefix originated cheap          | 955:3010  |                        |
| Prefix originated standard       | 955:3030  |                        |
| Prefix originated premium        | 955:3050  |                        |