komro: PeeringDB fix list
AS29413 · peeringdb.com/net/14657
3 things to fix in komro's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on komro's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in komro's PeeringDB record. Add one entry per connection with these values.
-
Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713From its IX-F export and website members listIPv4 185.0.21.16 IPv6 2001:7f8:7f::c:16 Speed 12500 Mbps (12.5G) RS peer Yes
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.
-
Problem PeeringDB has The export has Port speed differs 50G 100G - In the entry with IPv4 80.81.195.66: set Speed to 100000 (100G) (now 50000).
-
Problem PeeringDB has The export has Port speed differs 50G 100G - In the entry with IPv4 185.1.208.75: set Speed to 100000 (100G) (now 50000).
From ixreport.com/net/29413/: 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.