Meta: PeeringDB fix list

AS32934 · peeringdb.com/net/979

PeeringDB

27 things to fix in Meta's PeeringDB record, from what its exchanges publish: 8 to add, 13 to correct, 6 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Meta'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 Meta's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Bengaluru Bengaluru, India · PeeringDB 5045From its IX-F export

    2 connections, so 2 entries:

    IPv4151.158.193.5
    IPv62400:d180:77::5
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4151.158.193.6
    IPv62400:d180:77::6
    Speed100000 Mbps (100G)
    RS peerYes
  2. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789From 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. India Extreme IX Pune Pune, India · PeeringDB 4805From 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.

  4. Nigeria IXPN Abuja Abuja, Nigeria · PeeringDB 1870From its IX-F export
    IPv4196.216.150.10
    IPv62001:43f8:bb1:150::10
    Speed20000 Mbps (20G)
    RS peerNo
  5. Kenya KIXP - Nairobi Nairobi, Kenya · PeeringDB 236From 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.

  6. Netherlands LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its website members list
    IPv4185.1.32.25
    IPv62001:7f8:8f::a503:2934:1
    SpeedNot published
    RS peerNot published
  7. Denmark STHIX - Copenhagen Copenhagen, Denmark · PeeringDB 1869From its IX-F export

    2 connections, so 2 entries:

    IPv4185.1.88.37
    IPv62001:7f8:b0::3:2934:1
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4185.1.88.38
    IPv62001:7f8:b0::3:2934:2
    Speed10000 Mbps (10G)
    RS peerYes

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

  8. United States TPAIX Tampa, United States · PeeringDB 833From 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 (13)

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 B-IX Sofia, Bulgaria · PeeringDB 326
    ProblemPeeringDB hasThe export has
    Port speed differs4 × 100G260G
    • In the entry with IPv4 185.1.30.78: set Speed to 260000 (260G) (now 100000).
    • In the entry with IPv4 185.1.30.79: set Speed to 260000 (260G) (now 100000).
    • In the entry with IPv4 185.1.30.81: set Speed to 260000 (260G) (now 100000).
    • In the entry with IPv4 185.1.30.82: set Speed to 260000 (260G) (now 100000).
    • Add an entry: IPv4 –, IPv6 2001:7f8:8e:4::78, speed 260000 (260G), RS peer yes.
    • Add an entry: IPv4 –, IPv6 2001:7f8:8e:4::79, speed 260000 (260G), RS peer yes.
    • Add an entry: IPv4 –, IPv6 2001:7f8:8e:4::81, speed 260000 (260G), RS peer yes.
    • Add an entry: IPv4 –, IPv6 2001:7f8:8e:4::82, speed 260000 (260G), RS peer yes.
  2. Spain CATNIX Barcelona, Spain · PeeringDB 62
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 10G
    • In the entry with IPv4 193.242.98.139: set Speed to 10000 (10G) (now 100000).
    • In the entry with IPv4 193.242.98.158: set Speed to 10000 (10G) (now 100000).

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

  3. India DE-CIX Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G + 20G
    • In the entry with IPv4 103.228.174.158: set Speed to 20000 (20G) (now 100000).
  4. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB80.81.195.40 80.81.195.14180.81.194.40 80.81.195.40 80.81.195.141 80.81.195.176
    IPv6 address missing from PeeringDB2001:7f8::80a6:0:2 2001:7f8::80a6:0:32001:7f8::80a6:0:1 2001:7f8::80a6:0:2 2001:7f8::80a6:0:3 2001:7f8::80a6:0:4
    Port speed differs2 × 400G2 × 800G + 2 × 400G
    • In the entry with IPv4 80.81.195.141: set Speed to 800000 (800G) (now 400000).
    • In the entry with IPv4 80.81.195.40: set Speed to 800000 (800G) (now 400000).
    • Add an entry: IPv4 80.81.194.40, IPv6 2001:7f8::80a6:0:1, speed 400000 (400G), RS peer yes.
    • Add an entry: IPv4 80.81.195.176, IPv6 2001:7f8::80a6:0:4, speed 400000 (400G), RS peer yes.
  5. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G2 × 100G
    • In the entry with IPv4 89.46.145.202: set Speed to 100000 (100G) (now 200000).
    • In the entry with IPv4 89.46.145.60: set Speed to 100000 (100G) (now 200000).

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

  6. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.225.11 178.18.225.98178.18.225.11 178.18.225.98 178.18.236.82 178.18.236.83
    IPv6 address missing from PeeringDB2a03:5f80:4::225:11 2a03:5f80:4::225:982a03:5f80:4::225:11 2a03:5f80:4::225:98 2a03:5f80:4:2::236:82 2a03:5f80:4:2::236:83
    Port speed differs2 × 500G2 × 500G + 2 × 100G
    • Add an entry: IPv4 178.18.236.82, IPv6 2a03:5f80:4:2::236:82, speed 500000 (500G), RS peer yes.
    • Add an entry: IPv4 178.18.236.83, IPv6 2a03:5f80:4:2::236:83, speed 500000 (500G), 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.

  7. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    Port speed differs4 × 400G2 × 200G + 100G
    • In the entry with IPv4 123.108.10.170: set Speed to 100000 (100G) (now 400000).
    • In the entry with IPv4 123.108.10.171: set Speed to 100000 (100G) (now 400000).
    • In the entry with IPv4 123.108.9.129: set Speed to 200000 (200G) (now 400000).
    • In the entry with IPv4 123.108.9.130: set Speed to 200000 (200G) (now 400000).

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

  8. Nigeria IXPN Abuja Abuja, Nigeria · PeeringDB 1870
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB196.216.150.10 is AS63293 Meta AS63293196.216.150.10

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

  9. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 500G2 × 500G + 2 × 100G
  10. Philippines Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv4 address differs103.121.64.21 103.121.64.22163.223.201.21 163.223.201.22
    IPv6 address differs2400:efa0::3:2934:1 2400:efa0::3:2934:22001:df0:a940::3:2934:1 2001:df0:a940::3:2934:2
    • The entry with IPv4 103.121.64.21, IPv6 2400:efa0::3:2934:1 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 103.121.64.22, IPv6 2400:efa0::3:2934:2 isn't in the export: delete it if that connection is gone.
    • Add an entry: IPv4 163.223.201.22, IPv6 2001:df0:a940::3:2934:2, speed 100000 (100G), RS peer yes.
    • Add an entry: IPv4 163.223.201.21, IPv6 2001:df0:a940::3:2934:1, speed 100000 (100G), RS peer yes.
  11. United States MegaIX Ashburn Ashburn, United States · PeeringDB 1178
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.53.170.52206.53.170.52 206.53.170.56
    IPv6 address missing from PeeringDB2606:a980:0:3::342606:a980:0:3::34 2606:a980:0:3::38
    • Add an entry: IPv4 206.53.170.56, IPv6 2606:a980:0:3::38, RS peer no.

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

  12. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:67c:29f0::3:2934:3 2001:67c:29f0::3:2934:42001:67c:29f0::3:2934:3 2001:67c:29f0::5:360:4
    • In the entry with IPv4 185.1.226.119: set IPv6 to 2001:67c:29f0::5:360:4 (now 2001:67c:29f0::3:2934:4).

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

  13. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs4 × 400G200G
    • In the entry with IPv4 185.0.20.238: set Speed to 200000 (200G) (now 400000).
    • In the entry with IPv4 185.0.20.239: set Speed to 200000 (200G) (now 400000).
    • In the entry with IPv4 185.0.20.244: set Speed to 200000 (200G) (now 400000).
    • In the entry with IPv4 185.0.20.245: set Speed to 200000 (200G) (now 400000).

Check these entries (6)

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

  1. Bahrain Manama IX Manama, Bahrain · PeeringDB 2631Not on its website members list
    IPv477.69.248.104
    IPv62001:1a40:10::a503:2934:1
    Speed100000 Mbps (100G)

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

  2. Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868Not on its IX-F export
    IPv4212.237.192.127
    IPv62001:7f8:d:202::127
    Speed100000 Mbps (100G)
  3. Denmark Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 193Not on its IX-F export
    IPv4212.237.193.127
    IPv62001:7f8:d:203::127
    Speed100000 Mbps (100G)
  4. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.127
    IPv62001:7f8:d:fe::127
    Speed100000 Mbps (100G)
  5. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.127
    IPv62001:7f8:d:ff::127
    Speed100000 Mbps (100G)
  6. Oman Oman-IX Muscat, Oman · PeeringDB 4371Not on its website members list
    IPv496.9.145.100
    IPv62a0a:c743:1::a503:2934:2
    Speed100000 Mbps (100G)
    IPv496.9.145.63
    IPv62a0a:c743:1::a503:2934: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/32934/: 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.