Skip to main content

AS19755

CRUISE-NETENG-ASN

Cruise LLC

Registry

Authoritative registration data

AS number
19755
Name
CRUISE-NETENG-ASN
Organisation
Cruise LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS19755
128.177.102.0/24 IPv4 /24 not checked
162.223.176.0/24 IPv4 /24 not checked
162.223.177.0/24 IPv4 /24 not checked
162.223.178.0/24 IPv4 /24 not checked
199.73.125.0/24 IPv4 /24 not checked
199.73.127.0/24 IPv4 /24 not checked
208.184.11.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS19755 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 87 478
v4
AS6461 ZAYO-6461 76 439
v4
AS3356 LEVEL3 140 167
v4
AS12129 123NET 99 125
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS19755 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 1
v4

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.