ixreport

iManage

AS395505 · iManage

iManage, LLC

7Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
ContentType
RestrictivePeering policy
6Using the route servers
7To fix in PeeringDB
0Facilities in PeeringDB

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.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001: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).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:1:0:6:8f1:1
    Port speed differs8G4G
    • 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).
  3. United States MegaIX Ashburn Ashburn, United States · PeeringDB 1178
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2606: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.

  4. United States MegaIX Chicago Chicago, United States · PeeringDB 4507
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2606: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.

  5. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001: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.

  6. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001: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.

  1. United States ChIX Chicago, United States · PeeringDB 239Not on its website members list
    IPv4206.41.110.105
    IPv6–
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

Exchanges over time

02468Oct 3, 2026Nov 19, 20267
Show as a table
DateExchanges
Nov 19, 20267
Nov 18, 20267
Nov 17, 20267
Nov 16, 20267
Nov 15, 20267
Nov 14, 20267
Nov 13, 20267
Nov 12, 20267
Nov 11, 20267
Nov 10, 20267
Nov 9, 20267
Nov 8, 20267
Nov 7, 20267
Nov 6, 20267
Nov 5, 20267
Nov 4, 20267
Nov 3, 20267
Nov 2, 20267
Nov 1, 20267
Oct 31, 20267
Oct 30, 20267
Oct 29, 20267
Oct 28, 20267
Oct 27, 20267
Oct 26, 20267
Oct 25, 20267
Oct 24, 20267
Oct 23, 20267
Oct 22, 20267
Oct 21, 20267
Oct 20, 20267
Oct 19, 20267
Oct 18, 20267
Oct 17, 20267
Oct 16, 20267
Oct 15, 20267
Oct 14, 20267
Oct 13, 20267
Oct 12, 20267
Oct 11, 20267
Oct 10, 20267
Oct 9, 20267
Oct 8, 20267
Oct 7, 20267
Oct 6, 20267
Oct 5, 20267
Oct 4, 20267
Oct 3, 20267

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.

Exchanges

Total port capacity 68G across 7 exchanges.

United States ChIX Chicago, United States 206.41.110.105 10G PeeringDB only
United Kingdom LINX LON1 London, United Kingdom 195.66.227.64 10G 1 routes Both IPv6 not in PeeringDB
United Kingdom LINX LON2 London, United Kingdom 195.66.239.220 8G 1 routes Both IPv6 not in PeeringDBSpeed differs
United States MegaIX Ashburn Ashburn, United States 206.53.170.55 10G Yes Both IPv6 not in PeeringDB
United States MegaIX Chicago Chicago, United States 206.53.206.13 10G Yes Both IPv6 not in PeeringDB
Australia MegaIX Melbourne Melbourne, Australia 103.26.71.133 10G Yes Both IPv6 not in PeeringDB
Australia MegaIX Sydney Sydney, Australia 103.26.69.12 10G Yes Both IPv6 not in PeeringDB

iManage lists no facilities in PeeringDB.