Peering with Starlink

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

Users with specific engineering requirements can peer with Starlink over internet exchange points IXPs where Starlink peers.

IXPs are located in the Starlink points-of-presence (PoPs) and the IXP peering LAN and route servers can facilitate interconnection directly to your network.

The list of IXPs Starlink is connected to is maintained on the PeeringDB Public Peering Exchange Points list.

If you need to peer with Starlink, make sure you are connected to one IXPs in the geography of your home PoP. Once you are connected, you can peer with the IXP Route Server.

Finding your Home PoP

Starlink uses many PoPs around the world to route traffic. You can use the DNS PTR record for your Starlink's IP address to determine the home PoP. (e.g. 'dig -x' -> -> chcoilx1 is the CLLI code for Chicago, IL, USA).


Starlink home PoP may change for mobile users

If you move your Starlink to a new location, the home PoP may change and traffic routing is subject to change.

To manage this, Mobile Starlink users should peer at all possible IXPs. If traffic egresses from a different PoP without established peering, your traffic will be routed over the Internet.

How to Peer with an IXP Route Server

PeeringDB or the IXPs website are the best sources for IXP route server information. A PeeringDB account is generally required to view certain details.

How to Peer Directly with Starlink

Starlink can peer directly with customers via bilateral peering arrangements, however we recommend peering with the IXP route server to facilitate this with lower operational overheads for both parties.

Prerequisites to Peer with Starlink

  • 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 Starlink in PeeringDB
  • Up to date Maintainer, ASN, AS-SET, and Route/Route6 objects in an internet routing registry (IRR) and/or RADb.

Peering Technical Requirements

BGP and IP configuration requirements

  • BGP MD5 (Optional)
  • Only publicly routable addresses with valid IRRs should be announced to peering sessions. We do not accept Bogons.
  • Most specific prefix accepted /24 (IPv4), /48 (IPv6). Longer prefix announcements will be dropped
  • Only /31 IPv4 subnet sizes supported on PNIs.
  • No support for MEDs, EBGP multihop, or BFD