asn.dev

Observed topology

AS48732 PEERES-TELECOM PEERES-TELECOM

Unclassified RIPE

Upstreams 10 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 8
Upstream graph Who carries AS48732, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS48732 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48732: 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.

ASNetworkTypeFamiliesPaths seen
AS206120KOESIO Networks SASHostingIPv445
AS6939Hurricane Electric LLCTransitIPv629
AS174Cogent Communications, LLCTransitIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv62
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv62
AS212815Dyjix SASResidentialIPv62
AS9002RETN LimitedUnclassifiedIPv61
AS20766Association "Gitoyen"UnclassifiedIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS39801France IX Services SASUUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57080Yohan FRESNEAUUnclassifiedIPv699
AS212993Roger BeaumontUnclassifiedIPv634

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6142
AS57080Yohan FRESNEAUUnclassifiedIPv699
AS206120KOESIO Networks SASHostingIPv445
AS212993Roger BeaumontUnclassifiedIPv634
AS174Cogent Communications, LLCTransitIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv66
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv66
AS9002RETN LimitedUnclassifiedIPv64
AS212815Dyjix SASResidentialIPv62
AS20766Association "Gitoyen"UnclassifiedIPv41

All 12 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 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.