asn.dev

Observed topology

AS43797 RSNET2-AS RSNET2

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43797: 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 RostelecomResidentialIPv42,016
AS61280FGUP "GRCHC"UnclassifiedIPv463

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43795Budgetary institution in the field of information technologies of the Vologda region Center informacionnyh technologiiUnclassifiedIPv463
AS62422Federal Antimonopoly ServiceUnclassifiedIPv463
AS198688Federal Service for Transport Supervision (Rostransnadzor)UnclassifiedIPv463
AS200294State Autonomous Institution of the Republic of Dagestan "Information Technology Center"UnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv42,268
AS43795Budgetary institution in the field of information technologies of the Vologda region Center informacionnyh technologiiUnclassifiedIPv463
AS61280FGUP "GRCHC"UnclassifiedIPv463
AS62422Federal Antimonopoly ServiceUnclassifiedIPv463
AS198688Federal Service for Transport Supervision (Rostransnadzor)UnclassifiedIPv463
AS200294State Autonomous Institution of the Republic of Dagestan "Information Technology Center"UnclassifiedIPv463

Provenance

Where this comes from

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