RunRiver: PeeringDB fix list
AS133182 · peeringdb.com/net/39644
5 things to fix in RunRiver's PeeringDB record, from what its exchanges publish: 1 to correct, 4 to check. As of 2026-10-08 20:58 UTC.
Make the changes on RunRiver'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 (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 Port speed differs 10G 1G - In the entry with IPv4 123.108.11.208: set Speed to 1000 (1G) (now 10000).
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 (4)
In PeeringDB, but on none of the exchange's own lists. If RunRiver has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 103.162.254.130 IPv6 2001:df6:480:0:2:83e:0:1 Speed 100 Mbps (100M) -
IPv4 119.11.187.44 IPv6 2404:c8:0:a:0:13:3182:1 Speed 10000 Mbps (10G) -
IPv4 210.171.225.136 IPv6 2001:de8:8::13:3182:1 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 210.173.177.192 IPv6 2001:7fa:7:1:0:13:3182:1 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/133182/: 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.