Skip to main content

AS397018

CLOUDPROPELLER-AS01

Cloud Propeller

Registry

Authoritative registration data

AS number
397018
Name
CLOUDPROPELLER-AS01
Organisation
Cloud Propeller
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS397018
192.160.132.0/24 IPv4 /24 not checked
23.151.152.0/24 IPv4 /24 not checked
52.144.29.0/24 IPv4 /24 not checked
91.209.209.0/24 IPv4 /24 not checked
2602:fe42::/36 IPv6 /36 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 AS397018
Address families
Ohio IX: Ohio IX Public Peering LAN 400,000 Mbps IPv4 · IPv6

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 AS397018 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS397018 in AS paths

Observed upstreams
Families
AS396238 FAIRLAWNGIG-NET 150 760
v4
AS6939 HURRICANE 124 170
v6
AS10796 TWC-10796-MIDWEST 8 38
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS397018 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS20205 AMPLEX 1 5
v4 v6

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.