asn.dev

Observed topology

AS57354 SYSTEMA-AS SYSTEMA Ltd

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57354: 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
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6343
AS12389PJSC RostelecomResidentialIPv4 IPv6132
AS6939Hurricane Electric LLCTransitIPv490
AS50257JV A-Mobile Ltd.MobileIPv464
AS31500Global Network Management IncUnclassifiedIPv440
AS24482SG.GSHostingIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS49673Truenetwork LLCUnclassifiedIPv410
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60465National Bank of Republic of AbkhaziaUnclassifiedIPv486

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6359
AS12389PJSC RostelecomResidentialIPv4 IPv6155
AS6939Hurricane Electric LLCTransitIPv4103
AS60465National Bank of Republic of AbkhaziaUnclassifiedIPv486
AS31500Global Network Management IncUnclassifiedIPv466
AS50257JV A-Mobile Ltd.MobileIPv464
AS24482SG.GSHostingIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS49673Truenetwork LLCUnclassifiedIPv412
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv412

Provenance

Where this comes from

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