ixreport

NETFORMS: PeeringDB fix list

AS198346 · peeringdb.com/net/18803

PeeringDB

One thing to fix in NETFORMS's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on NETFORMS'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. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:7f::43 2001:7f8:7f::235 2001:7f8:7f::248 2001:7f8:7f::249
    Port speed differs4 × 100G42.5G
    • In the entry with IPv4 185.0.20.235: set IPv6 to 2001:7f8:7f::235 (now empty); set Speed to 42500 (42.5G) (now 100000).
    • In the entry with IPv4 185.0.20.248: set IPv6 to 2001:7f8:7f::248 (now empty); set Speed to 42500 (42.5G) (now 100000).
    • In the entry with IPv4 185.0.20.249: set IPv6 to 2001:7f8:7f::249 (now empty); set Speed to 42500 (42.5G) (now 100000).
    • In the entry with IPv4 185.0.20.43: set IPv6 to 2001:7f8:7f::43 (now empty); set Speed to 42500 (42.5G) (now 100000).

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