RASCOM: PeeringDB fix list
AS20764 · peeringdb.com/net/2501
7 things to fix in RASCOM's PeeringDB record, from what its exchanges publish: 4 to add, 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on RASCOM'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 (4)
On the exchange's own member list, but not in RASCOM's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.170.65 IPv6 2001:7f8:9e::511c:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.1.210.82 IPv6 2001:7f8:3d::511c:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.1.208.73 IPv6 2001:7f8:44::511c:0:1 Speed 100000 Mbps (100G) RS peer Yes -
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its IX-F export and website members listIPv4 185.1.32.148 IPv6 2001:7f8:8f::a502:764:1 Speed 100000 Mbps (100G) 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 20G 50T - In the entry with IPv4 194.68.128.188: set Speed to 50000000 (50T) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 20G 50T - In the entry with IPv4 194.68.123.188: set Speed to 50000000 (50T) (now 20000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If RASCOM has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713Not on its IX-F export or website members listIPv4 91.213.211.172 IPv6 2001:7f8:7f::172 Speed 20000 Mbps (20G)
From ixreport.com/net/20764/: 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.