Skip to main content

AS2072

FR-RENATER-REVE

Reseau REVE

Registry

Authoritative registration data

AS number
2072
Name
FR-RENATER-REVE
Organisation
Reseau REVE
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS2072
185.4.251.0/24 IPv4 /24 not checked
192.93.214.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 AS2072 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS2072 in AS paths

Observed upstreams
Families
AS8218 NEO-ASN 675 1,228
v4
AS2200 FR-RENATER 534 702
v4
AS6939 HURRICANE 19 20
v4
AS20764 RASCOM-AS 4 4
v4
AS34019 HIVANE 2 4
v4
AS6057 6057 2 2
v4
AS34177 CELESTE-AS 2 2
v4
AS35280 F5 2 2
v4
AS39351 ESAB-AS 2 2
v4
AS4455 1 1
v4
AS6758 AS6758 1 1
v4
AS7713 telkomnet-as-ap 1 1
v4
AS20766 1 1
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS2072 in AS paths

Observed downstreams
Families
AS199255 263 686
v4
AS2094 FR-TELECOM-MANAGEMENT-SUDPARIS 472 620
v4

No rows match “”.

Showing of

Uncertain adjacencies

26 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.