Skip to main content

AS395505

IMANAGE

iManage, LLC

Registry

Authoritative registration data

AS number
395505
Name
IMANAGE
Organisation
iManage, LLC
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

0

Total announced

11

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS395505
130.12.172.0/23 IPv4 /23 not checked
165.193.189.0/24 IPv4 /24 not checked
205.219.118.0/24 IPv4 /24 not checked
205.219.119.0/24 IPv4 /24 not checked
206.25.45.0/24 IPv4 /24 not checked
207.82.22.0/24 IPv4 /24 not checked
207.82.23.0/24 IPv4 /24 not checked
38.45.163.0/24 IPv4 /24 not checked
65.151.0.0/24 IPv4 /24 not checked
65.151.1.0/24 IPv4 /24 not checked
8.12.29.0/24 IPv4 /24 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS395505
Address families
ChIX 10,000 Mbps IPv4
LINX LON1: Main 10,000 Mbps IPv4
LINX LON2 8,000 Mbps IPv4
MegaIX Ashburn: MegaIX 10,000 Mbps IPv4
MegaIX Chicago 10,000 Mbps IPv4
MegaIX Melbourne: MegaIX 10,000 Mbps IPv4
MegaIX Sydney: MegaIX 10,000 Mbps IPv4

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS395505 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

36 networks seen before AS395505 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS395505 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

31 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.