asn.dev

Observed topology

AS62429 CSTNET

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62429: 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
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4230
AS29076Citytelecom LLCHostingIPv4 IPv688
AS1299Arelion Sweden ABTransitIPv4 IPv675
AS35598INETCOM CARRIER LLCUnclassifiedIPv463
AS24482SG.GSHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS62255BiMajLink d.o.o.UnclassifiedIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209558PREMIUM KEA GRUP LLCUnclassifiedIPv416
AS210281EcoConnect LLCUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4230
AS1299Arelion Sweden ABTransitIPv4 IPv6103
AS29076Citytelecom LLCHostingIPv4 IPv693
AS35598INETCOM CARRIER LLCUnclassifiedIPv468
AS210281EcoConnect LLCUnclassifiedIPv422
AS209558PREMIUM KEA GRUP LLCUnclassifiedIPv416
AS24482SG.GSHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS62255BiMajLink d.o.o.UnclassifiedIPv47

Provenance

Where this comes from

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