ixreport

WEBCONEX: PeeringDB fix list

AS211448 · peeringdb.com/net/26795

PeeringDB

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

Make the changes on WEBCONEX'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. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.125.184none
    • In the entry with IPv4 185.1.125.184: set IPv4 to (empty) (now 185.1.125.184).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 178.18.237.107: set Speed to 10000 (10G) (now 1000).

    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/211448/: 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.