iManage: PeeringDB fix list
AS395505 · peeringdb.com/net/17139
7 things to fix in iManage's PeeringDB record, from what its exchanges publish: 6 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on iManage's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (6)
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:4::6:8f1:1 - In the entry with IPv4 195.66.227.64: set IPv6 to 2001:7f8:4::6:8f1:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4:1:0:6:8f1:1 Port speed differs 8G 4G - In the entry with IPv4 195.66.239.220: set IPv6 to 2001:7f8:4:1:0:6:8f1:1 (now empty); set Speed to 4000 (4G) (now 8000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 206.53.170.55 206.53.170.10 206.53.170.55 IPv6 address missing from PeeringDB none 2606:a980:0:3::a 2606:a980:0:3::37 - In the entry with IPv4 206.53.170.55: set IPv6 to 2606:a980:0:3::37 (now empty).
- Add an entry: IPv4 206.53.170.10, IPv6 2606:a980:0:3::a, RS peer no.
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 2606:a980:0:d::d - In the entry with IPv4 206.53.206.13: set IPv6 to 2606:a980:0:d::d (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:dea:0:30::85 - In the entry with IPv4 103.26.71.133: set IPv6 to 2001:dea:0:30::85 (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:dea:0:10::10c - In the entry with IPv4 103.26.69.12: set IPv6 to 2001:dea:0:10::10c (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If iManage has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.41.110.105 IPv6 – Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/395505/: 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.