asn.dev

Observed topology

AS49675 SKBKONTUR-AS SKB Kontur Production JSC

Unclassified RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49675: 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 RostelecomResidentialIPv4401
AS3216PJSC "Vimpelcom"MobileIPv4201
AS2854LLC Orange Business ServicesUnclassifiedIPv4 IPv6129
AS201706SERVICEPIPE LLCUnclassifiedIPv4122
AS8359MTS PJSCMobileIPv496
AS12668LLC "KomTehCentr"UnclassifiedIPv444
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv424
AS8470JSC MacomnetUnclassifiedIPv620
AS24482SG.GSHostingIPv4 IPv615
AS49673Truenetwork LLCUnclassifiedIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201268SKB Kontur Production JSCUnclassifiedIPv4126

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4401
AS3216PJSC "Vimpelcom"MobileIPv4255
AS2854LLC Orange Business ServicesUnclassifiedIPv4 IPv6157
AS201268SKB Kontur Production JSCUnclassifiedIPv4126
AS201706SERVICEPIPE LLCUnclassifiedIPv4122
AS8359MTS PJSCMobileIPv496
AS12668LLC "KomTehCentr"UnclassifiedIPv488
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv424
AS8470JSC MacomnetUnclassifiedIPv620
AS24482SG.GSHostingIPv4 IPv615

All 11 adjacent →

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.