PeakFactory: PeeringDB fix list

AS49206 · peeringdb.com/net/9610

PeeringDB

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

Make the changes on PeakFactory'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. Hungary BIX Budapest, Hungary · PeeringDB 55
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.188.137.58193.188.137.58 193.188.137.93
    IPv6 address missing from PeeringDB2001:7f8:35::4:9206:12001:7f8:35::4:9206:1 2001:7f8:35::4:9206:2
    • Add an entry: IPv4 193.188.137.93, IPv6 2001:7f8:35::4:9206:2, speed 10000 (10G), RS peer yes.
  2. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G200G
    • In the entry with IPv4 185.0.21.149: set Speed to 200000 (200G) (now 400000).
    • In the entry with IPv4 185.0.21.247: set Speed to 200000 (200G) (now 400000).

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