ixreport

ByteDance: PeeringDB fix list

AS396986 · peeringdb.com/net/19428

PeeringDB

19 things to fix in ByteDance's PeeringDB record, from what its exchanges publish: 15 to add, 2 to correct, 2 to check. As of 2026-10-08 18:53 UTC.

Make the changes on ByteDance'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 (15)

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

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From 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. United States Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142From its website members list
    IPv4206.72.210.95 206.72.211.150 206.72.211.154
    IPv62001:504:13::210:95 2001:504:13::211:150 2001:504:13::211:154
    SpeedNot published
    RS peerNot published

    The exchange lists several addresses but not which go together: add one entry for each IPv4 and IPv6 pair.

  3. United States DE-CIX New York New York, United States · PeeringDB 804From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4206.82.104.38
    IPv62001:504:36:0:6:eba:0:1
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4206.82.104.53
    IPv62001:504:36:0:6:eba:0:2
    Speed100000 Mbps (100G)
    RS peerYes
  4. Qatar Doha IX Doha, Qatar · PeeringDB 4715From its IX-F export
    IPv4194.42.47.76
    IPv62001:7f8:162:0:6:eba:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  5. Germany ERA-IX Frankfurt Frankfurt, Germany · PeeringDB 4630From its IX-F export and website members list
    IPv4185.0.27.93
    IPv62001:7f8:15e::93
    Speed100000 Mbps (100G)
    RS peerYes

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

  6. France ERA-IX Paris Paris, France · PeeringDB 4985From its IX-F export and website members list
    IPv4195.60.85.144
    IPv62001:7f8:16f::144
    Speed100000 Mbps (100G)
    RS peerYes

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

  7. Austria ERA-IX Vienna Vienna, Austria · PeeringDB 5029From 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.

  8. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.237.36
    IPv62a03:5f80:4:2::237:36
    Speed100000 Mbps (100G)
    RS peerYes

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

  9. Hong Kong HKIX Hong Kong, Hong Kong · PeeringDB 42From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  10. Ireland INEX LAN1 Dublin, Ireland · PeeringDB 48From 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.

  11. United States MegaIX Ashburn Ashburn, United States · PeeringDB 1178From its IX-F export

    2 connections, so 2 entries:

    IPv4206.53.170.53
    IPv62606:a980:0:3::35
    SpeedNot published
    RS peerYes
    IPv4206.53.170.54
    IPv62606:a980:0:3::36
    SpeedNot published
    RS peerYes

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

  12. United States MegaIX Los Angeles Los Angeles, United States · PeeringDB 1175From its IX-F export

    2 connections, so 2 entries:

    IPv4206.53.172.16
    IPv62606:a980:0:5::10
    SpeedNot published
    RS peerYes
    IPv4206.53.172.21
    IPv62606:a980:0:5::15
    SpeedNot published
    RS peerYes

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

  13. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.100
    IPv62001:7f8:d:fb::100
    SpeedNot published
    RS peerYes
  14. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.100
    IPv62001:7f8:d:fc::100
    SpeedNot published
    RS peerYes
  15. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4185.0.20.90
    IPv62001:7f8:7f::90
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4185.0.21.90
    IPv62001:7f8:7f::c:90
    Speed100000 Mbps (100G)
    RS peerYes

Correct these entries (2)

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. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.227.42185.1.227.41 185.1.227.42
    IPv6 address missing from PeeringDB2001:67c:29f0::39:6986:12001:67c:29f0::39:6986:1 2001:67c:29f0::39:6986:2
    • Add an entry: IPv4 185.1.227.41, IPv6 2001:67c:29f0::39:6986:2, 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.

  2. France nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France · PeeringDB 4705
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.14.36185.1.14.36 185.1.14.44
    IPv6 address missing from PeeringDB2001:7f8:12e::39:6986:12001:7f8:12e::39:6986:1 2001:7f8:12e::39:6986:2
    Port speed differs100G2 × 100G
    • Add an entry: IPv4 185.1.14.44, IPv6 2001:7f8:12e::39:6986:2, speed 100000 (100G), 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.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If ByteDance has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30Not on its website members list
    IPv4210.171.225.198
    IPv62001:de8:8::39:6986:2
    Speed100000 Mbps (100G)
    IPv4210.171.225.98
    IPv62001:de8:8::39:6986:1
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  2. Bahrain Manama IX Manama, Bahrain · PeeringDB 2631Not on its website members list
    IPv477.69.248.15
    IPv62001:1a40:10:0:a500:39:6986:1
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

From ixreport.com/net/396986/: 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.