asn.dev

Observed topology

AS12392 ASVOO Orange Belgium SA

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12392: 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
AS1299Arelion Sweden ABTransitIPv4 IPv63,367
AS5511Orange S.A.TransitIPv4 IPv61,712
AS9002RETN LimitedUnclassifiedIPv4 IPv6667
AS6696VERIXI SAUnclassifiedIPv4 IPv6234
AS6461Zayo BandwidthTransitIPv4 IPv6160
AS34019Hivane AssociationUnclassifiedIPv4 IPv6117
AS48185team.blue NVUnclassifiedIPv4 IPv6117

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200133HUmani SocietyUnclassifiedIPv497
AS60650Nethys S.AUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv63,474
AS5511Orange S.A.TransitIPv4 IPv61,735
AS9002RETN LimitedUnclassifiedIPv4 IPv6684
AS6696VERIXI SAUnclassifiedIPv4 IPv6237
AS6461Zayo BandwidthTransitIPv4 IPv6160
AS34019Hivane AssociationUnclassifiedIPv4 IPv6120
AS48185team.blue NVUnclassifiedIPv4 IPv6120
AS200133HUmani SocietyUnclassifiedIPv497
AS60650Nethys S.AUnclassifiedIPv459

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.