Skip to main content

AS62141

CNRHONE-AS

COMPAGNIE NATIONALE DU RHONE S.A.

Registry

Authoritative registration data

AS number
62141
Name
CNRHONE-AS
Organisation
COMPAGNIE NATIONALE DU RHONE S.A.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS62141
185.38.92.0/22 IPv4 /22 RPKI valid

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 AS62141
Address families
France-IX AURA: lyonix-peering 11,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 AS62141 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS62141 in AS paths

Observed upstreams
Families
AS30781 JAGUAR-AS 153 190
v4
AS39801 FRANCE-IX-L3P 42 63
v4
AS174 COGENT-174 36 39
v4
AS6939 HURRICANE 30 32
v4
AS43100 FRANCE-IX-LYN-RS 6 6
v4
AS34019 HIVANE 3 5
v4
AS35625 EUROFIBER-FRANCE 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS62141 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS2027 MilkyWan 1 1
v4
AS29075 IELO 1 1
v4
AS56987 AS-ABACLOUDA 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.