JK-Network: PeeringDB fix list

AS207705 · peeringdb.com/net/29437

PeeringDB

2 things to fix in JK-Network's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on JK-Network'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.35none
    • In the entry with IPv4 185.1.125.35: set IPv4 to (empty) (now 185.1.125.35).
  2. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export103.158.187.73none
    • In the entry with IPv4 103.158.187.73: set IPv4 to (empty) (now 103.158.187.73).

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