SwissIX Route Servers: PeeringDB fix list

AS42476 · peeringdb.com/net/722

PeeringDB

One thing to fix in SwissIX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on SwissIX Route Servers'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 (1)

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 SwissIX Zurich, Switzerland · PeeringDB 60
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB91.206.52.252 91.206.53.25391.206.52.252 91.206.53.66 91.206.53.253
    IPv6 address missing from PeeringDB2001:7f8:24::a5ec:a:1 2001:7f8:24::a5ec:a:22001:7f8:24::a5ec:a:1 2001:7f8:24::a5ec:a:2 2001:7f8:24::a5ec:b:dead
    Port speed differs2 × 20G3 × 20G
    • Add an entry: IPv4 91.206.53.66, IPv6 2001:7f8:24::a5ec:b:dead, speed 20000 (20G), 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.

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