asn.dev

Observed topology

AS51904 UTEX-AS Shchurov Mikhail Yurievich

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51904: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv474
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv434
AS57304JSC "RetnNet"UnclassifiedIPv416
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42
AS62255BiMajLink d.o.o.UnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51538Lavrentyev Aleksandr ArkadievichUnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4180
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv482
AS51538Lavrentyev Aleksandr ArkadievichUnclassifiedIPv466
AS57724DDOS-GUARD LTDUnclassifiedIPv441
AS57304JSC "RetnNet"UnclassifiedIPv428
AS62255BiMajLink d.o.o.UnclassifiedIPv410
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43

Provenance

Where this comes from

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