asn.dev

Observed topology

AS206407 RECONN-SPB

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206407: 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
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv668
AS31500Global Network Management IncUnclassifiedIPv4 IPv630
AS12722RECONN LLCHostingIPv42
AS24482SG.GSHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49426LInTeCS ltd (Laboratory of Information Technologies and Computer Systems)UnclassifiedIPv4195

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv6197
AS49426LInTeCS ltd (Laboratory of Information Technologies and Computer Systems)UnclassifiedIPv4195
AS31500Global Network Management IncUnclassifiedIPv4 IPv690
AS24482SG.GSHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS12722RECONN LLCHostingIPv42

Provenance

Where this comes from

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