Observed topology

AS2072 FR-RENATER-REVE Reseau REVE

Unclassified RIPE

Upstreams 8 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

Upstream graph Who carries AS2072, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS2072 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2072: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

AS	Network	Type	Families	Paths seen
AS2200	Renater	Education	IPv4	63
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	46
AS6939	Hurricane Electric LLC	Transit	IPv4	10
AS20766	Association "Gitoyen"	Unclassified	IPv4	1
AS24482	SG.GS	Hosting	IPv4	1
AS34927	iFog GmbH	Hosting	IPv4	1
AS37721	Virtual Technologies & Solutions	Residential	IPv4	1
AS50628	Leonix Telecom SAS	Unclassified	IPv4	1

Transit

Downstream networks

inferred

Networks for which AS2072 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS199255	Groupement Interet Economique REVE	Unclassified	IPv4	120
AS2094	Renater	Unclassified	IPv4	109

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS2072 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	212
AS2200	Renater	Education	IPv4	126
AS199255	Groupement Interet Economique REVE	Unclassified	IPv4	120
AS2094	Renater	Unclassified	IPv4	109
AS6939	Hurricane Electric LLC	Transit	IPv4	10
AS20766	Association "Gitoyen"	Unclassified	IPv4	1
AS24482	SG.GS	Hosting	IPv4	1
AS34927	iFog GmbH	Hosting	IPv4	1
AS37721	Virtual Technologies & Solutions	Residential	IPv4	1
AS50628	Leonix Telecom SAS	Unclassified	IPv4	1

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.