FASTER CZ: PeeringDB fix list
AS24641 · peeringdb.com/net/15600
2 things to fix in FASTER CZ's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on FASTER CZ'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 FASTER CZ's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 91.210.16.149 IPv6 2001:7f8:14::ad:2 Speed 20000 Mbps (20G) RS peer Yes IPv4 91.210.17.30 IPv6 2001:7f8:14::ad:1 Speed 20000 Mbps (20G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
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.
-
Problem PeeringDB has The export has IPv4 address differs 91.213.211.173 185.0.20.173 Port speed differs 10G 1.25G - In the entry with IPv4 91.213.211.173: set IPv4 to 185.0.20.173 (now 91.213.211.173); set Speed to 1250 (1.25G) (now 10000).
From ixreport.com/net/24641/: 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.