asn.dev

Observed topology

AS42610 NCNET-AS OJSC National Cable Networks

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42610: 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
AS12389PJSC RostelecomResidentialIPv4 IPv61,499
AS1299Arelion Sweden ABTransitIPv4500

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6863PJSC RostelecomUnclassifiedIPv4744
AS25531PJSC RostelecomUnclassifiedIPv4682
AS29069PJSC RostelecomUnclassifiedIPv4372
AS8629Moscow Center of New Telecommunication Technologies JSCUnclassifiedIPv462
AS60473LLC CTIUnclassifiedIPv427
AS197379INVITRO-Information technology LLCUnclassifiedIPv422
AS64512AS64512UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv63,518
AS6863PJSC RostelecomUnclassifiedIPv4853
AS25531PJSC RostelecomUnclassifiedIPv4682
AS1299Arelion Sweden ABTransitIPv4500
AS29069PJSC RostelecomUnclassifiedIPv4372
AS8629Moscow Center of New Telecommunication Technologies JSCUnclassifiedIPv462
AS60473LLC CTIUnclassifiedIPv427
AS197379INVITRO-Information technology LLCUnclassifiedIPv422
AS64512AS64512UnclassifiedIPv41

Provenance

Where this comes from

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