asn.dev

Observed topology

AS203597 STEKSPB-AS

Unclassified RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS203597: 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
AS20764CJSC RASCOMUnclassifiedIPv4 IPv662
AS3216PJSC "Vimpelcom"MobileIPv4 IPv657
AS51178JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv625
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv620
AS6939Hurricane Electric LLCTransitIPv412
AS24482SG.GSHostingIPv4 IPv63
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv63
AS9002RETN LimitedUnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42

All 12 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4 IPv662
AS3216PJSC "Vimpelcom"MobileIPv4 IPv657
AS51178JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv625
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv620
AS6939Hurricane Electric LLCTransitIPv412
AS24482SG.GSHostingIPv4 IPv63
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv63
AS9002RETN LimitedUnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42

All 12 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.