asn.dev

Observed topology

AS197695 AS-REGRU "Domain names registrar REG.RU", Ltd

Hosting RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS197695: 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
AS39561"Domain names registrar REG.RU", LtdUnclassifiedIPv4 IPv69,386
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv48,506
AS199599Telecom-Birzha, LLCUnclassifiedIPv46,481
AS6939Hurricane Electric LLCTransitIPv41,804
AS8492"OBIT" Ltd.UnclassifiedIPv41,612
AS28917Fiord Networks, UABUnclassifiedIPv4420
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4388
AS39134EDINAYA SET LIMITED LIABILITY COMPANYUnclassifiedIPv4 IPv6295
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4288
AS24482SG.GSHostingIPv4 IPv6195

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43489JSC "RU-CENTER"UnclassifiedIPv4176
AS210550Andrey KrukoverUnclassifiedIPv4 IPv6155
AS202696Trusted Network LLCUnclassifiedIPv476
AS204822Alvist LLCUnclassifiedIPv463
AS211183AdminVPS OOOUnclassifiedIPv442

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS39561"Domain names registrar REG.RU", LtdUnclassifiedIPv4 IPv69,762
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv48,506
AS199599Telecom-Birzha, LLCUnclassifiedIPv46,535
AS6939Hurricane Electric LLCTransitIPv41,804
AS8492"OBIT" Ltd.UnclassifiedIPv41,612
AS28917Fiord Networks, UABUnclassifiedIPv4428
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4394
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4336
AS39134EDINAYA SET LIMITED LIABILITY COMPANYUnclassifiedIPv4 IPv6295
AS24482SG.GSHostingIPv4 IPv6195

Provenance

Where this comes from

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