Solido: PeeringDB fix list
AS38915 · peeringdb.com/net/3057
2 things to fix in Solido'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 Solido'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 Solido's PeeringDB record. Add one entry per connection with these values.
-
IPv4 80.249.209.205 IPv6 2001:7f8:1::a503:8915:1 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.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.239.119.87 193.239.116.35 193.239.119.87 IPv6 address missing from PeeringDB 2001:7f8:13::a503:8915:2 2001:7f8:13::a503:8915:1 2001:7f8:13::a503:8915:2 - Add an entry: IPv4 193.239.116.35, IPv6 2001:7f8:13::a503:8915:1, 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.
From ixreport.com/net/38915/: 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.