Source
r/StarlinkEngineering•
virtuallynathan

Starlink Internet Infrastructure

Starlink runs on their own network now, via AS14593.

SpaceX publishes a GeoIP feed here: https://geoip.starlinkisp.net/feed.csv

IP Assignments to SpaceX Services:

  • 143.131.0.0/20 (ARIN)

  • 206.214.224.0/20 (ARIN)

  • 205.174.156.0/23 (ARIN)

  • 198.54.100.0/22 (ARIN)

  • 149.19.108.0/23 (ARIN)

  • 135.129.240.0/20 (ARIN)

  • 135.129.0.0/23 (ARIN)

  • 135.129.112.0/20 (ARIN)

  • 135.129.0.0/18 (ARIN)

  • 149.19.108.0/23 (ARIN)

  • 198.54.103.0/24 (ARIN)

  • 204.48.8.0/21 (ARIN)

  • 206.214.224.0/20 (ARIN)

  • 206.224.64.0/19 (ARIN)

  • 216.147.120.0/21 (ARIN)

  • 98.97.0.0/17 (ARIN)

  • 98.97.128.0/18 (ARIN)

  • 170.203.64.0/19 (ARIN)

  • 170.203.192.0/19 (ARIN)

  • 129.222.0.0/16 (ARIN)

  • 145.224.64.0/18 (ARIN)

  • 198.54.100.0/22 (ARIN)

  • 2605:59C0::/28 (ARIN)

  • AS397763 (ARIN) [this ASN has never been seen on the Internet]

  • 2a0d:3340::/29 (RIPE)

  • 162.43.192.0/22 (RIPE)

  • 176.116.124.0/23 (RIPE)

  • 188.95.144.0/23 (RIPE)

  • 217.65.136.0/23 (RIPE)

  • 217.65.138.0/23 (RIPE)

  • 217.65.140.0/23 (RIPE)

  • 217.65.142.0/23 (RIPE)

  • 188.92.248.0/21 (RIPE)

  • 2406:2d40::/32 (APNIC)

  • 103.152.126.0/23 (APNIC)

  • 103.235.92.0/22 (APNIC)

  • 206.83.96.0/19 (APNIC)

  • 149.19.160.0/20 (LACNIC)

  • 206.83.96.0/19 (APNIC)

  • 2803:9810::/32 (LACNIC)

Total IPv4 Addresses as of Mar 3 2022: 227,072

ARIN Assignments to SpaceX:

  • AS14593
  • 2620:134:B000::/40
  • 192.31.242.0/23
  • 199.175.188.0/24
  • AS27277 (SpaceX Corporate)

IPv4 announcements by SpaceX AS14593:

EDIT: Feb 2022 -- AS14593 has been expanding rapidly in it's PoPs on PeeringDB, and it's prefixes advertised. Users have begun reporting having been assigned IPs from this ASN.

This ASN has transit from Zayo, Lumen, GTT, Telia, Hurricane Electric, and Seabras1 (GRU only). PoPs are currently listed as SEA, ORD, NYC, LAX, ATL, DFW, GRU, MEX, SCL, LON, FRA, SYD, and LOS.

North America:

Peering:

  • Seattle IX - 2x2x100G (SEA)
  • CIX-ATL - 2x100G (ATL)
  • ChIX - 2x100G (ORD)
  • DE-CIX NYC - 2x100G (NYC)
  • Any2West - 2x100G (LAX)
  • Any2Denver - 2x100G Turn-up (DEN)
  • Equinix Dallas - 2x100G (DFW)

Prefixes:

  • 98.97.56.0/21 - lsancax1 (LAX)
  • 135.129.8.0/21 - lsancax1 (LAX)
  • 98.97.168.0/21 - atlagax1 (ATL)
  • 98.97.176.0/21 - atlagax1 (ATL)
  • 98.97.72.0/24 - dllstxx1 (DFW)
  • 98.97.80.0/21 - dllstxx1 (DFW)
  • 98.97.88.0/21 - dllstxx1 (DFW)
  • 98.97.64.0/21 - sttlwax1 (SEA)
  • 135.129.0.0/21 - sttlwax1 (SEA)
  • 98.97.32.0/21 - sttlwax1 (SEA)
  • 98.97.40.0/21 - sttlwax1 (SEA)
  • 98.97.48.0/21 - sttlwax1 (SEA)
  • 98.97.96.0/21 - sttlwax1 (SEA)
  • 98.97.104.0/21 - sttlwax1 (SEA)
  • 98.97.112.0/21 - sttlwax1 (SEA)
  • 98.97.120.0/21 - sttlwax1 (SEA)
  • 98.97.128.0/21 - sttlwax1 (SEA)
  • 98.97.136.0/21 - sttlwax1 (SEA)
  • 98.97.144.0/21 - sttlwax1 (SEA)
  • 98.97.152.0/21 - sttlwax1 (SEA)
  • 98.97.160.0/21 - sttlwax1 (SEA)
  • 170.203.192.0/21 - sttlwax1 (SEA)
  • 170.203.200.0/21 - sttlwax1 (SEA)
  • 170.203.208.0/21 - sttlwax1 (SEA)
  • 170.203.216.0/21 - sttlwax1 (SEA)
  • 170.203.64.0/21 - sttlwax1 (SEA)
  • 170.203.72.0/21 - sttlwax1 (SEA)
  • 170.203.80.0/21 - sttlwax1 (SEA)
  • 170.203.88.0/21 - sttlwax1 (SEA)
  • 98.97.0.0/21 - chcoilx1 (ORD)
  • 98.97.8.0/21 - chcoilx1 (ORD)
  • 129.222.0.0/21 - chcoilx1 (ORD)
  • 129.222.8.0/21 - chcoilx1 (ORD)
  • 129.222.16.0/21 - chcoilx1 (ORD)
  • 129.222.24.0/21 - chcoilx1 (ORD)
  • 129.222.32.0/21 - chcoilx1 (ORD)
  • 129.222.40.0/21 - chcoilx1 (ORD)
  • 129.222.48.0/21 - chcoilx1 (ORD)
  • 129.222.56.0/21 - chcoilx1 (ORD)
  • 129.222.64.0/21 - chcoilx1 (ORD)
  • 129.222.72.0/21 - chcoilx1 (ORD)
  • 129.222.80.0/21 - chcoilx1 (ORD)
  • 129.222.88.0/21 - chcoilx1 (ORD)
  • 129.222.96.0/21 - chcoilx1 (ORD)
  • 129.222.104.0/21 - chcoilx1 (ORD)
  • 129.222.112.0/21 - chcoilx1 (ORD)
  • 129.222.120.0/21 - chcoilx1 (ORD)
  • 129.222.128.0/21 - chcoilx1 (ORD)
  • 129.222.136.0/21 - chcoilx1 (ORD)
  • 206.224.72.0/21 - chcoilx1 (ORD)
  • 98.97.16.0/21 - nwyynyx1 (NYC)
  • 98.97.24.0/21 - nwyynyx1 (NYC)
  • 129.222.144.0/21 - nwyynyx1 (NYC)
  • 129.222.152.0/21 - nwyynyx1 (NYC)
  • 129.222.160.0/21 - nwyynyx1 (NYC)
  • 129.222.168.0/21 - nwyynyx1 (NYC)
  • 129.222.176.0/21 - nwyynyx1 (NYC)
  • 129.222.184.0/21 - nwyynyx1 (NYC)
  • 129.222.192.0/21 - nwyynyx1 (NYC)
  • 129.222.200.0/21 - nwyynyx1 (NYC)
  • 129.222.208.0/21 - nwyynyx1 (NYC)
  • 129.222.216.0/21 - nwyynyx1 (NYC)
  • 129.222.224.0/21 - nwyynyx1 (NYC)
  • 129.222.232.0/21 - nwyynyx1 (NYC)
  • 129.222.240.0/21 - nwyynyx1 (NYC)
  • 129.222.248.0/21 - nwyynyx1 (NYC)
  • 135.129.57.0/24 - TBD (DFW?)
  • 135.129.58.0/24 - TBD (ATL?)
  • 135.129.61.0/24 - TBD (NYC?)
  • 135.129.62.0/24 - TBD (ORD?)
  • 135.129.63.0/24 - TBD (LAX?)
  • 206.224.90.0/23 - TBD
  • 216.147.120.0/21 - TBD (DEN)
  • 98.97.75.0/24 - TBD (ATL?)
  • 98.97.73.0/24 - TBD (SEA?)

APAC

Peering:

  • EdgeIX - 2x100G (SYD)
  • EdgeIX - 2x100G (PER?)

Prefixes:

  • 206.83.112.0/21 - sydyaus1 (SYD)
  • 206.83.124.0/24 - tkyojpn1 (TYO)
  • 206.83.125.0/24 - tkyojpn1 (TYO)

South/Central America:

Peering:

  • PTT BR / IX.Br - 2x100G (GRU)
  • PIT Chile - 2x100G (SCL)

Prefixes:

  • 149.19.164.0/22 - splobra1 (GRU)
  • 149.19.172.0/22 - splobra1 (GRU)
  • 135.129.55.0/24 - TBD (SCL?)
  • 135.129.60.0/24 - TBD (MEX?)
  • 149.19.168.0/23 - qrtomex1 (QRO/MEX)
  • 149.19.170.0/24 - qrtomex1 (QRO/MEX)
  • 149.19.171.0/24 - qrtomex1 (QRO/MEX)
  • 135.129.19.0/24 - TBD (SCL?)
  • 138.84.32.0/22 - sntochl1 (SCL)
  • 138.84.36.0/24 - TBD
  • 2803:9810:2000::/48 (SCL)

EMEA:

Peering:

  • LINX - 2x100G (LHR)
  • DE-CIX - 2x100G (FRA)

Prefixes:

  • 135.129.49.0/24 - TBD (FRA?)
  • 135.129.50.0/24 - TBD (LHR?)
  • 135.129.48.0/24 - TBD (MAD?)
  • 145.224.64.0/21 - lndngbr1 (LHR)
  • 145.224.72.0/21 - frntdeu1 (FRA)
  • 145.224.80.0/21 - lndngbr1 (LHR)
  • 145.224.88.0/22 - lndngbr1 (LHR)
  • 145.224.96.0/21 - frntdeu1 (FRA)
  • 145.224.104.0/22 - TBD (FRA?)
  • 145.224.108.0/22 - frntdeu1 (FRA)
  • 145.224.94.0/24 - frntdeu1 (FRA)
  • 145.224.95.0/24 - frntdeu1 (FRA)
  • 145.224.124.0/22 - mdrdesp1 (MAD)
  • 145.224.92.0/23 - mdrdesp1 (MAD)
  • 188.92.248.0/24 - TBD

Infra: 9 /24s.

  • 149.19.108.0/23 - Starlink Infra (Routers?)
  • 192.31.243.0/24 - Starlink Infra (SEA)
  • 198.54.103.0/24 - Starlink Infra (SEA)
  • 206.224.80.0/23 - Starlink Infra? (SEA)
  • 206.224.84.0/23 - Starlink Infra? (SEA)
  • 198.54.100.0/24 - Starlink Infra (Anycast?)
  • 2620:134:b0ff::/48- Starlink Infra (SEA)

Total Customer IPv4 Addresses announced: 163,072

IPv4 announcements by Google AS36492:

NA:

  • 143.131.0.0/24 - LAX1
  • 143.131.1.0/24 - LAX2
  • 206.214.224.0/24 - LAX (advertised from SEA)
  • 206.214.225.0/24 - "reserved" (advertised from SEA)
  • 206.214.226.0/24 - LAX3
  • 206.214.227.0/24 - LAX4
  • 135.129.240.0/24 - LAX5
  • 143.131.2.0/24 - SEA1
  • 143.131.3.0/24 - SEA2
  • 206.214.232.0/24 - SEA5
  • 206.214.233.0/24 - SEA6
  • 206.214.234.0/24 - SEA3
  • 206.214.235.0/24 - SEA4
  • 143.131.4.0/24 - ORD1
  • 143.131.5.0/24 - ORD2
  • 135.129.242.0/24 - ORD5
  • 143.131.6.0/24 - LGA1
  • 143.131.7.0/24 - LGA2
  • 206.214.230.0/24 - LGA3
  • 206.214.231.0/24 - LGA4
  • 135.129.244.0 - LGA5
  • 143.131.8.0/24 - MIA1
  • 143.131.9.0/24 - MIA2
  • 143.131.10.0/24 - DFW1
  • 143.131.11.0/24 - DFW2
  • 143.131.12.0/24 - DEN1
  • 143.131.13.0/24 - DEN2
  • 143.131.14.0/24 - SJC1 (advertised from ORD)
  • 143.131.15.0/24 - SJC2 (advertised from ORD)
  • 206.214.236.0/24 - SJC3
  • 206.214.237.0/24 - SJC4
  • 205.174.156.0/24 - IAD1 (advertised from NYC)
  • 205.174.157.0/24 - IAD2 (advertised from NYC)
  • 206.214.238.0/24 - IAD3
  • 206.214.239.0/24 - IAD4

SA:

  • 149.19.160.0/24 - SCL1
  • 149.19.161.0/24 - SCL2
  • 149.19.162.0/24 - BOG1
  • 149.19.163.0/24 - BOG2

APAC:

  • 103.152.126.0/24 - SYD1 - New Zealand (?)
  • 103.152.127.0/24 - SYD2
  • 103.235.92.0/24 - TBD - maxmind JP
  • 103.235.93.0/24 - TBD - maxmind JP
  • 103.235.94.0/24 - TBD - maxmind SG
  • 103.235.95.0/24 - TBD - maxmind SG

EU:

  • 162.43.192.0/24 - MAD1
  • 162.43.193.0/24 - MAD2
  • 162.43.194.0/24 - LHR3
  • 162.43.195.0/24 - LHR4
  • 176.116.124.0/24 - LHR1
  • 176.116.125.0/24 - LHR2
  • 188.95.144.0/24 - FRA1
  • 188.95.145.0/24 - FRA2
  • 217.65.136.0/24 - SOF1
  • 217.65.137.0/24 - SOF2
  • 217.65.138.0/24 - TBD
  • 217.65.139.0/24 - TBD
  • 217.65.140.0/24 - TBD
  • 217.65.141.0/24 - TBD (MAD?)
  • 217.65.142.0/24 - SOF1
  • 217.65.143.0/24 - SOF2

Google also announces these IPv6 prefixes for SpaceX, but they are harder to locate and have no PTR records.

If you run a traceroute/mtr to any of these, you'll notice they enter Google's network at the nearest AS15169 interconnect, as Google (generally) announces these routes everywhere, opting to use their own backbone instead of the internet to carry the traffic. The latency to near-ish to the last hop is about right for the locations. They seem to be hot-potato outbound, and cold-potato inbound.

GeoIP Locations

  • Amsterdam
  • Athens
  • Atlanta
  • Auckland
  • Berlin
  • Bratislava
  • Brussels
  • Bucharest
  • Budapest
  • Cairo
  • Calgary
  • Chicago
  • Chisinau
  • Copenhagen
  • Dallas
  • Delhi
  • Denver
  • Dublin
  • Frankfurt
  • Kyiv
  • Lisbon
  • Ljubljana
  • London
  • Los Angeles
  • Madrid
  • Mexico City
  • Miami
  • Montreal
  • New York
  • Nuku'alofa
  • Paris
  • Prague
  • Puerto Rico
  • Rome
  • San Jose
  • Santiago
  • Santo Domingo
  • Sao Paulo
  • Seattle
  • Singapore
  • Sofia
  • Stockholm
  • Sydney
  • Tokyo
  • Toronto
  • Vancouver
  • Vienna
  • Vilnius
  • Warsaw
  • Washington DC
  • Winnipeg
  • Zagreb
  • Zurich

How it might work

There's a lot of "stuff" to do with a big satellite network. You've got a ton of ground stations, satellites, and users. Satellites pass overhead, and may transition between users and ground stations -- you need to be able to keep a TCP flow alive and transmitting while all of this is happening. You need to collect data on performance. You need to do authorization, access control, accounting. Given the rapid performance increase of software-based packet forwarding with things like DPDK, you'd probably do all of this on commodity hardware. To test all of this, and build/scale it rapidly, you might partner with a cloud provider with a very large high performance network, who wants to help you out because they invested $1bn.

SpaceX hired for a "Sr. Software Engineer (Starlink Network)" which said "Experience in C/C++ for high performance systems. IP routing and fast path development, experience working on DPDK and/or VPP a major plus"

Sources:

  • stat.ripe.net
  • bgp.tools
  • arin.net
  • peeringdb.com
  • traceroute/mtr from my servers
  • hunches/speculation from working on networking stuff for a long time

Posted Jul 7, 2021, 4:04 PM UTC · edited

2423
Loading comments…