ixreport

Melbikomas: PeeringDB fix list

AS56630 · peeringdb.com/net/11217

2 things to fix in Melbikomas's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

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

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. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.47.64185.1.47.43 185.1.47.64
    IPv6 address missing from PeeringDB2001:7f8:36::dd36:0:12001:7f8:36::dd36:0:1 2001:7f8:36::dd36:0:2
    • Add an entry: IPv4 185.1.47.43, IPv6 2001:7f8:36::dd36:0:2, speed 100000 (100G), RS peer yes.
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs3 × 10G2 × 10G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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