RBMNET: PeeringDB fix list
AS212518 · peeringdb.com/net/24909
2 things to fix in RBMNET's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on RBMNET'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.
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv6 2602:fed2:fff:ffff:6::4a: set Speed to 1000 (1G) (now 100).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.0.30.81 - In the entry with IPv6 2001:7f8:11c:1:0:21:2518:1: set IPv4 to 185.0.30.81 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/212518/: 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.