IPTP Networks: PeeringDB fix list
AS41095 · peeringdb.com/net/1046
4 things to fix in IPTP Networks's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on IPTP Networks'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 IPTP Networks's PeeringDB record. Add one entry per connection with these values.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions 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 Port speed differs 100G 10G - In the entry with IPv4 195.66.225.64: set Speed to 10000 (10G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 10G 20G - In the entry with IPv4 217.29.66.94: set Speed to 20000 (20G) (now 10000).
From ixreport.com/net/41095/: 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.