ixreport

meteversecloud: PeeringDB fix list

AS54994 · peeringdb.com/net/9470

PeeringDB

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

Make the changes on meteversecloud'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 (4)

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

  1. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277From its IX-F export and website members list
    IPv4185.1.192.8
    IPv62001:7f8:a0::d6d2:0:1
    Speed20000 Mbps (20G)
    RS peerYes
  2. Mexico DE-CIX Mexico Mexico City, Mexico · PeeringDB 4525From its IX-F export
    IPv445.68.64.28
    IPv62806:424::d6d2:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  3. Portugal GigaPIX - LAN 1 Lisbon, Portugal · PeeringDB 72From its IX-F export and website members list
    IPv4193.136.250.217
    IPv62001:7f8:a:1::217
    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.

  4. United States KCIX Kansas City, United States · PeeringDB 249From its IX-F export and website members list
    IPv4206.51.7.251
    IPv62001:504:1b:1::251
    Speed100000 Mbps (100G)
    RS peerNot published

Correct these entries (14)

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. Djibouti AMS-IX Djibouti Djibouti, Djibouti · PeeringDB 967
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:9c1:1:0:a505:4994:1
    • In the entry with IPv4 196.223.38.205: set IPv6 to 2001:43f8:9c1:1:0:a505:4994:1 (now empty).

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

  2. South Africa CINX Cape Town, South Africa · PeeringDB 344
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 196.223.22.111: set Speed to 100000 (100G) (now 10000).

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

  3. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G40G
    • In the entry with IPv4 185.1.170.57: set Speed to 40000 (40G) (now 1000).
  4. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs1G40G
    • In the entry with IPv4 185.1.210.16: set Speed to 40000 (40G) (now 1000).
  5. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G40G
    • In the entry with IPv4 185.1.208.65: set Speed to 40000 (40G) (now 1000).
  6. Philippines GetaFIX Manila Manila, Philippines · PeeringDB 2345
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB103.104.19.176103.104.19.115 103.104.19.176
    IPv6 address missing from PeeringDB2401:fdc0::5:4994:22401:fdc0::5:4994:1 2401:fdc0::5:4994:2
    Port speed differs100G2 × 100G
    • Add an entry: IPv4 103.104.19.115, IPv6 2401:fdc0::5:4994:1, 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.

  7. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.236.207178.18.236.207 178.18.236.227
    IPv6 address missing from PeeringDB2a03:5f80:4:2::236:2072a03:5f80:4:2::236:207 2a03:5f80:4:2::236:227
    • Add an entry: IPv4 178.18.236.227, IPv6 2a03:5f80:4:2::236:227, speed 10000 (10G), 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.

  8. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB123.108.12.34123.108.12.34 123.108.12.108
    IPv6 address missing from PeeringDB2001:7fa:2:5::4302001:7fa:2:5::430 2001:7fa:2:5::47a
    Port speed differs200G2 × 200G
    • Add an entry: IPv4 123.108.12.108, IPv6 2001:7fa:2:5::47a, 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.

  9. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.216.148.165196.216.148.165 196.216.148.166
    IPv6 address missing from PeeringDB2001:43f8:bb1::1652001:43f8:bb1::165 2001:43f8:bb1::166
    Port speed differs40G100G + 40G
    • In the entry with IPv4 196.216.148.165: set Speed to 100000 (100G) (now 40000).
    • Add an entry: IPv4 196.216.148.166, IPv6 2001:43f8:bb1::166, speed 40000 (40G), RS peer yes.
  10. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB119.11.186.143119.11.186.143 119.11.187.218 119.11.187.219
    IPv6 address missing from PeeringDB2404:c8:0:a:0:5:4994:12404:c8:0:a:0:5:4994:1 2404:c8:0:a:0:5:4994:2 2404:c8:0:a:0:5:4994:3
    Port speed differs40G3 × 200G
    • In the entry with IPv4 119.11.186.143: set Speed to 200000 (200G) (now 40000).
    • Add an entry: IPv4 119.11.187.218, IPv6 2404:c8:0:a:0:5:4994:2, speed 200000 (200G), RS peer yes.
    • Add an entry: IPv4 119.11.187.219, IPv6 2404:c8:0:a:0:5:4994:3, speed 200000 (200G), RS peer yes.
  11. Philippines Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv4 address differs103.121.64.34163.223.201.34
    IPv6 address differs2400:efa0::5:4994:12001:df0:a940::5:4994:1
    • In the entry with IPv4 103.121.64.34: set IPv4 to 163.223.201.34 (now 103.121.64.34); set IPv6 to 2001:df0:a940::5:4994:1 (now 2400:efa0::5:4994:1).
  12. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:b:100:1d1:a5d5:4994:237none
    Port speed differs10G20G
    • In the entry with IPv4 217.29.66.237: set IPv6 to (empty) (now 2001:7f8:b:100:1d1:a5d5:4994:237); set Speed to 20000 (20G) (now 10000).
  13. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G + 10G

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

  14. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs4 × 200G3 × 200G + 100G
    • In the entry with IPv4 103.16.102.142: set Speed to 100000 (100G) (now 200000).

Check these entries (1)

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

  1. Ghana Accra Internet Exchange LBG Accra, Ghana · PeeringDB 4259Not on its website members list
    IPv4196.60.12.47
    IPv62001:7f8:b6:5::d6d2: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/54994/: 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.