Free Pro: PeeringDB fix list
AS30781 · peeringdb.com/net/731
5 things to fix in Free Pro's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Free Pro'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 (2)
On the exchange's own member list, but not in Free Pro's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.94.23 IPv6 2001:7f8:b6::783d:1 Speed 10000 Mbps (10G) RS peer Yes -
Hopus Paris, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France · PeeringDB 1320From its website members listThe exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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 100G - In the entry with IPv4 80.81.194.172: set Speed to 100000 (100G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 20G 100G - In the entry with IPv4 185.1.47.134: set Speed to 100000 (100G) (now 20000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Free Pro has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 185.1.177.7 IPv6 2001:7f8:fa::7 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/30781/: 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.