Feral Hosting: PeeringDB fix list
AS200052 · peeringdb.com/net/6141
9 things to fix in Feral Hosting's PeeringDB record, from what its exchanges publish: 1 to add, 8 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Feral Hosting'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 Feral Hosting's PeeringDB record. Add one entry per connection with these values.
-
The 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 (8)
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:7f8:1:0:a500:20:52:1 - In the entry with IPv4 80.249.211.10: set IPv6 to 2001:7f8:1:0:a500:20:52: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:12a::5 - In the entry with IPv4 185.1.240.5: set IPv6 to 2001:7f8:12a::5 (now empty).
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 2a03:5f80:4::224:69 2a03:5f80:4:2::236:84 Port speed differs 2 × 10G 10G - In the entry with IPv4 178.18.224.69: set IPv6 to 2a03:5f80:4::224:69 (now empty).
- In the entry with IPv4 178.18.236.84: set IPv6 to 2a03:5f80:4:2::236:84 (now empty).
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:4::3:d74:1 Port speed differs 10G 100G - In the entry with IPv4 195.66.226.194: set IPv6 to 2001:7f8:4::3:d74:1 (now empty); set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4:1:0:3:d74:1 - In the entry with IPv4 195.66.238.194: set IPv6 to 2001:7f8:4:1:0:3:d74:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:17::3:d74:1 - In the entry with IPv4 5.57.81.90: set IPv6 to 2001:7f8:17::3:d74: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.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:13::a520:52:1 - In the entry with IPv4 193.239.117.86: set IPv6 to 2001:7f8:13::a520:52: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:b7::a520:52:1 - In the entry with IPv4 185.1.222.43: set IPv6 to 2001:7f8:b7::a520:52: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/200052/: 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.