EPIX POLMIX: PeeringDB fix list
AS201054 · peeringdb.com/net/14282
2 things to fix in EPIX POLMIX'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 EPIX POLMIX'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 EPIX POLMIX's PeeringDB record. Add one entry per connection with these values.
-
6 connections, so 6 entries:
IPv4 195.149.232.115 IPv6 2001:7f8:27::20:1054:1 Speed Not published RS peer Not published IPv4 195.149.232.209 IPv6 2001:7f8:27::20:1054:2 Speed Not published RS peer Not published IPv4 195.149.233.109 IPv6 2001:7f8:27::20:1054:5 Speed Not published RS peer Not published IPv4 195.149.233.108 IPv6 2001:7f8:27::20:1054:4 Speed Not published RS peer Not published IPv4 195.149.233.176 IPv6 2001:7f8:27::20:1054:6 Speed Not published RS peer Not published IPv4 195.149.232.179 IPv6 2001:7f8:27::20:1054:3 Speed Not published RS peer Not published 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 89.46.144.240 89.46.145.42 89.46.145.49 89.46.145.93 89.46.144.240 89.46.145.42 89.46.145.49 89.46.145.93 89.46.145.154 89.46.145.208 IPv6 address missing from PeeringDB 2001:678:3ac::f67 2001:678:3ac::f68 2001:678:3ac::f69 2001:678:3ac::f70 2001:678:3ac::588 2001:678:3ac::f67 2001:678:3ac::f68 2001:678:3ac::f69 2001:678:3ac::f70 2001:678:3ac::f71 Port speed differs 4 × 10G 6 × 10G - Add an entry: IPv4 89.46.145.208, IPv6 2001:678:3ac::588, speed 10000 (10G), RS peer yes.
- Add an entry: IPv4 89.46.145.154, IPv6 2001:678:3ac::f71, speed 10000 (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.
From ixreport.com/net/201054/: 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.