ixreport

SpaceX Starlink: PeeringDB fix list

AS14593 · peeringdb.com/net/18747

PeeringDB

17 things to fix in SpaceX Starlink's PeeringDB record, from what its exchanges publish: 8 to add, 9 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on SpaceX Starlink's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (8)

On the exchange's own member list, but not in SpaceX Starlink's PeeringDB record. Add one entry per connection with these values.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. Malaysia MyIX Kuala Lumpur, Malaysia · PeeringDB 250From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  4. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846From its IX-F export
    IPv4194.68.128.215
    IPv62001:7f8:d:fe::215
    SpeedNot published
    RS peerYes
  5. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.215
    IPv62001:7f8:d:fb::215
    SpeedNot published
    RS peerYes
  6. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70From its IX-F export
    IPv4194.68.123.215
    IPv62001:7f8:d:ff::215
    SpeedNot published
    RS peerYes
  7. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.215
    IPv62001:7f8:d:fc::215
    SpeedNot published
    RS peerYes
  8. Bulgaria TurkIX Sofia Sofia, Bulgaria · PeeringDB 4186From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (9)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Nigeria AMS-IX Lagos Lagos, Nigeria · PeeringDB 2381
    ProblemPeeringDB hasThe export has
    Port speed differs300G600G
    • In the entry with IPv4 196.60.58.56: set Speed to 600000 (600G) (now 300000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 500G
    • In the entry with IPv4 185.1.192.227: set Speed to 500000 (500G) (now 100000).
    • In the entry with IPv4 185.1.192.242: set Speed to 500000 (500G) (now 100000).
  3. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 300G2 × 400G
    • In the entry with IPv4 206.82.105.46: set Speed to 400000 (400G) (now 300000).
    • In the entry with IPv4 206.82.105.47: set Speed to 400000 (400G) (now 300000).
  4. Philippines GetaFIX Manila Manila, Philippines · PeeringDB 2345
    ProblemPeeringDB hasThe export has
    Port speed differs100G600G
    • In the entry with IPv4 103.104.19.82: set Speed to 600000 (600G) (now 100000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  5. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.216.148.129196.216.148.128 196.216.148.129
    IPv6 address missing from PeeringDB2001:43f8:bb1::1292001:43f8:bb1::128 2001:43f8:bb1::129
    Port speed differs600G600G + 300G
    • Add an entry: IPv4 196.216.148.128, IPv6 2001:43f8:bb1::128, speed 300000 (300G), RS peer yes.
  6. United States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G2 × 400G
    • In the entry with IPv4 206.51.7.23: set Speed to 400000 (400G) (now 200000).
    • In the entry with IPv4 206.51.7.7: set Speed to 400000 (400G) (now 200000).
  7. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 500G
    • In the entry with IPv4 195.66.224.70: set Speed to 500000 (500G) (now 100000).
    • In the entry with IPv4 195.66.224.75: set Speed to 500000 (500G) (now 100000).
  8. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs200G400G
    • In the entry with IPv4 217.29.67.231: set Speed to 400000 (400G) (now 200000).
  9. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.60.8.40196.60.8.40 196.60.11.58
    IPv6 address missing from PeeringDB2001:43f8:6d0::402001:43f8:6d0::40 2001:43f8:6d0::11:58
    Port speed differs200G2 × 200G
    • Add an entry: IPv4 196.60.11.58, IPv6 2001:43f8:6d0::11:58, speed 200000 (200G), RS peer yes.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

From ixreport.com/net/14593/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.