Future Publishing: PeeringDB fix list
AS20596 · peeringdb.com/net/8696
3 things to fix in Future Publishing's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Future Publishing'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 Future Publishing's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.66.254.12 IPv6 2001:7f8:4:4::5074:1 Speed 10000 Mbps (10G) RS peer Yes
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 IPv4 address missing from PeeringDB 195.66.226.199 195.66.226.199 195.66.231.176 IPv6 address missing from PeeringDB 2001:7f8:4::5074:1 2001:7f8:4::5074:1 2001:7f8:4::5074:2 Port speed differs 1G 2 × 10G - In the entry with IPv4 195.66.226.199: set Speed to 10000 (10G) (now 1000).
- Add an entry: IPv4 195.66.231.176, IPv6 2001:7f8:4::5074:2, speed 10000 (10G), RS peer yes.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 195.66.238.199 195.66.236.106 195.66.238.199 IPv6 address missing from PeeringDB 2001:7f8:4:1::5074:1 2001:7f8:4:1::5074:1 2001:7f8:4:1::5074:2 Port speed differs 1G 2 × 10G - In the entry with IPv4 195.66.238.199: set Speed to 10000 (10G) (now 1000).
- Add an entry: IPv4 195.66.236.106, IPv6 2001:7f8:4:1::5074:2, speed 10000 (10G), RS peer yes.
From ixreport.com/net/20596/: 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.