asn.dev

Observed topology

AS47104 PROLINK Prolink MO.ru Ltd.

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47104: 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 LLCUnclassifiedIPv4114
AS31133PJSC MegaFonMobileIPv451
AS62255BiMajLink d.o.o.UnclassifiedIPv418
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51054OOO "TransKom"UnclassifiedIPv4427
AS60986ZagorodTelecom LLCUnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4457
AS51054OOO "TransKom"UnclassifiedIPv4427
AS31133PJSC MegaFonMobileIPv4102
AS62255BiMajLink d.o.o.UnclassifiedIPv449
AS24482SG.GSHostingIPv47
AS60986ZagorodTelecom LLCUnclassifiedIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv45

Provenance

Where this comes from

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