asn.dev

Observed topology

AS50187 BWC BaikalWestCom LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50187: 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 RostelecomResidentialIPv4 IPv6620
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6243
AS1299Arelion Sweden ABTransitIPv4 IPv6233
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6171
AS44267EN+ TELECOM LLCUnclassifiedIPv4 IPv6157
AS3216PJSC "Vimpelcom"MobileIPv4130
AS24482SG.GSHostingIPv425
AS49673Truenetwork LLCUnclassifiedIPv425

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42897BaikalWestCom LtdUnclassifiedIPv4 IPv6351
AS56535Alpari Ltd.UnclassifiedIPv4180
AS213480StroyProektServis LLCUnclassifiedIPv461
AS211587LLC "ASF"UnclassifiedIPv459
AS57629LLC IVI.RUHostingIPv634
AS44345Mayak LLCUnclassifiedIPv412

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6793
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6479
AS42897BaikalWestCom LtdUnclassifiedIPv4 IPv6351
AS1299Arelion Sweden ABTransitIPv4 IPv6349
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6239
AS44267EN+ TELECOM LLCUnclassifiedIPv4 IPv6195
AS56535Alpari Ltd.UnclassifiedIPv4180
AS3216PJSC "Vimpelcom"MobileIPv4175
AS213480StroyProektServis LLCUnclassifiedIPv461
AS211587LLC "ASF"UnclassifiedIPv459

All 15 adjacent →

Provenance

Where this comes from

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