asn.dev

Observed topology

AS202309 RADIBASE

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202309: 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
AS57344Telehouse EADResidentialIPv4 IPv6189
AS1299Arelion Sweden ABTransitIPv4105
AS3223Voxility LLPHostingIPv4 IPv685
AS31083Telepoint LtdHostingIPv413
AS57463NetIX Communications JSCUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199388RDB BULGARIA Ltd.UnclassifiedIPv460
AS214471Radibase EOODUnclassifiedIPv458
AS199123Radibase EOODUnclassifiedIPv426

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS57344Telehouse EADResidentialIPv4 IPv6266
AS1299Arelion Sweden ABTransitIPv4150
AS3223Voxility LLPHostingIPv4 IPv685
AS199388RDB BULGARIA Ltd.UnclassifiedIPv460
AS214471Radibase EOODUnclassifiedIPv458
AS199123Radibase EOODUnclassifiedIPv426
AS31083Telepoint LtdHostingIPv419
AS34224Neterra Ltd.UnclassifiedIPv415
AS57463NetIX Communications JSCUnclassifiedIPv45

Provenance

Where this comes from

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