asn.dev

Observed topology

AS202486 SKYTELECOM +

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202486: 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 IPv6657
AS31500Global Network Management IncUnclassifiedIPv4317
AS3216PJSC "Vimpelcom"MobileIPv4 IPv672
AS8359MTS PJSCMobileIPv461
AS24482SG.GSHostingIPv4 IPv620
AS37721Virtual Technologies & SolutionsResidentialIPv418
AS49673Truenetwork LLCUnclassifiedIPv418
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv418
AS50673Serverius Holding B.V.UnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215455GENERAL IT RUS LLCUnclassifiedIPv444

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6683
AS31500Global Network Management IncUnclassifiedIPv4320
AS3216PJSC "Vimpelcom"MobileIPv4 IPv684
AS8359MTS PJSCMobileIPv462
AS215455GENERAL IT RUS LLCUnclassifiedIPv444
AS24482SG.GSHostingIPv4 IPv620
AS49673Truenetwork LLCUnclassifiedIPv419
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv419
AS37721Virtual Technologies & SolutionsResidentialIPv418
AS50673Serverius Holding B.V.UnclassifiedIPv45

Provenance

Where this comes from

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