asn.dev

Observed topology

AS50254 SKY-EN

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50254: 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 LLCUnclassifiedIPv493
AS31500Global Network Management IncUnclassifiedIPv446
AS3216PJSC "Vimpelcom"MobileIPv438
AS29076Citytelecom LLCHostingIPv46
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31225Sky Engineering LLCUnclassifiedIPv4635
AS44715Globalcom Ltd.UnclassifiedIPv465
AS62333OOO "Yulia"UnclassifiedIPv465
AS60519OOO Shishkin Les HoldingUnclassifiedIPv464
AS57843GK INTERLOGICA LLCUnclassifiedIPv442
AS211446"A GROUP" LLCUnclassifiedIPv413

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS31225Sky Engineering LLCUnclassifiedIPv4635
AS35598INETCOM CARRIER LLCUnclassifiedIPv4539
AS31500Global Network Management IncUnclassifiedIPv4177
AS3216PJSC "Vimpelcom"MobileIPv4118
AS1299Arelion Sweden ABTransitIPv4116
AS44715Globalcom Ltd.UnclassifiedIPv465
AS62333OOO "Yulia"UnclassifiedIPv465
AS60519OOO Shishkin Les HoldingUnclassifiedIPv464
AS29076Citytelecom LLCHostingIPv446
AS57843GK INTERLOGICA LLCUnclassifiedIPv442

All 18 adjacent →

Provenance

Where this comes from

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