RuiNetwork: PeeringDB fix list
AS211575 · peeringdb.com/net/27067
4 things to fix in RuiNetwork's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 2 to check. As of 2026-10-08 18:53 UTC.
Make the changes on RuiNetwork'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 RuiNetwork's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.0.24.198 IPv6 2001:7f8:aa::198 Speed 10000 Mbps (10G) 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 missing from PeeringDB none 33.0.0.70 Port speed differs 1G 10G - In the entry with IPv6 2a0f:7803:fc60:aaaa::2115:75: set IPv4 to 33.0.0.70 (now empty); set Speed to 10000 (10G) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If RuiNetwork has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 2602:fed2:fff:ffff:6::fa Speed 1000 Mbps (1G) -
IPv4 103.158.187.167 IPv6 2a0f:5707:ffe3::167 Speed 1000 Mbps (1G)
From ixreport.com/net/211575/: 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.