iManage
AS395505 · iManage
iManage, LLC
Tools: Where can I peer with iManage? · Where should iManage peer next? · Compare iManage with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
7 things to fix in iManage's PeeringDB record, from what its exchanges publish: 6 to correct, 1 to check. As of 2026-11-19 18:41 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 IPv6 address missing from PeeringDB none 2606:a980:0:3::37 - In the entry with IPv4 206.53.170.55: set IPv6 to 2606:a980:0:3::37 (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 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.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 7 |
| Nov 18, 2026 | 7 |
| Nov 17, 2026 | 7 |
| Nov 16, 2026 | 7 |
| Nov 15, 2026 | 7 |
| Nov 14, 2026 | 7 |
| Nov 13, 2026 | 7 |
| Nov 12, 2026 | 7 |
| Nov 11, 2026 | 7 |
| Nov 10, 2026 | 7 |
| Nov 9, 2026 | 7 |
| Nov 8, 2026 | 7 |
| Nov 7, 2026 | 7 |
| Nov 6, 2026 | 7 |
| Nov 5, 2026 | 7 |
| Nov 4, 2026 | 7 |
| Nov 3, 2026 | 7 |
| Nov 2, 2026 | 7 |
| Nov 1, 2026 | 7 |
| Oct 31, 2026 | 7 |
| Oct 30, 2026 | 7 |
| Oct 29, 2026 | 7 |
| Oct 28, 2026 | 7 |
| Oct 27, 2026 | 7 |
| Oct 26, 2026 | 7 |
| Oct 25, 2026 | 7 |
| Oct 24, 2026 | 7 |
| Oct 23, 2026 | 7 |
| Oct 22, 2026 | 7 |
| Oct 21, 2026 | 7 |
| Oct 20, 2026 | 7 |
| Oct 19, 2026 | 7 |
| Oct 18, 2026 | 7 |
| Oct 17, 2026 | 7 |
| Oct 16, 2026 | 7 |
| Oct 15, 2026 | 7 |
| Oct 14, 2026 | 7 |
| Oct 13, 2026 | 7 |
| Oct 12, 2026 | 7 |
| Oct 11, 2026 | 7 |
| Oct 10, 2026 | 7 |
| Oct 9, 2026 | 7 |
| Oct 8, 2026 | 7 |
| Oct 7, 2026 | 7 |
| Oct 6, 2026 | 7 |
| Oct 5, 2026 | 7 |
| Oct 4, 2026 | 7 |
| Oct 3, 2026 | 7 |
Map
Where iManage's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| ChIX Chicago, United States | 10G | PeeringDB only | |
| LINX LON1 London, United Kingdom | 10G | Both IPv6 not in PeeringDB | |
| LINX LON2 London, United Kingdom | 8G | Both IPv6 not in PeeringDBSpeed differs | |
| MegaIX Ashburn Ashburn, United States | 10G | Both IPv6 not in PeeringDB | |
| MegaIX Chicago Chicago, United States | 10G | Both IPv6 not in PeeringDB | |
| MegaIX Melbourne Melbourne, Australia | 10G | Both IPv6 not in PeeringDB | |
| MegaIX Sydney Sydney, Australia | 10G | Both IPv6 not in PeeringDB |
iManage lists no facilities in PeeringDB.