asn.dev

Observed topology

AS47586 Business-Svyaz Dmitriy V. Kozmenko

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47586: 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
AS8359MTS PJSCMobileIPv4 IPv6363
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6265
AS6939Hurricane Electric LLCTransitIPv499
AS24482SG.GSHostingIPv431
AS49673Truenetwork LLCUnclassifiedIPv431
AS25091IP-Max SAUnclassifiedIPv419

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50257JV A-Mobile Ltd.MobileIPv4322
AS52043LLC "Multiservice"UnclassifiedIPv4240
AS51607IpMedia Sochi LTDUnclassifiedIPv4118
AS48275Republican Unitary Enterprise "Abkhazsvyaz"UnclassifiedIPv496
AS57629LLC IVI.RUHostingIPv632
AS48498Sochi-Online Ltd.UnclassifiedIPv431
AS56529RuaD-Group LLCUnclassifiedIPv413

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6986
AS50257JV A-Mobile Ltd.MobileIPv4516
AS8359MTS PJSCMobileIPv4 IPv6511
AS52043LLC "Multiservice"UnclassifiedIPv4240
AS6939Hurricane Electric LLCTransitIPv4183
AS51607IpMedia Sochi LTDUnclassifiedIPv4118
AS48275Republican Unitary Enterprise "Abkhazsvyaz"UnclassifiedIPv496
AS24482SG.GSHostingIPv436
AS49673Truenetwork LLCUnclassifiedIPv436
AS57629LLC IVI.RUHostingIPv632

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.