FEROMEDIA: PeeringDB fix list
AS197667 · peeringdb.com/net/11308
3 things to fix in FEROMEDIA's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on FEROMEDIA'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 FEROMEDIA's PeeringDB record. Add one entry per connection with these values.
-
IPv4 178.216.40.22 IPv6 2001:7f8:5b::22 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 (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 IPv6 address missing from PeeringDB none 2001:678:3ac::58 Port speed differs 10G 20G - In the entry with IPv4 89.46.144.58: set IPv6 to 2001:678:3ac::58 (now empty); set Speed to 20000 (20G) (now 10000).
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 IPv6 address missing from PeeringDB none 2001:7f8:27::19:7667:1 - In the entry with IPv4 195.149.232.117: set IPv6 to 2001:7f8:27::19:7667:1 (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/197667/: 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.