asn.dev

Observed topology

AS197013 SPRINTEL-SRO Sprintel s.r.o.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197013: 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
AS39392SH.cz s.r.o.HostingIPv4 IPv6254
AS6939Hurricane Electric LLCTransitIPv455
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv45
AS20562Broadband Hosting B.V.HostingIPv45
AS24482SG.GSHostingIPv45
AS29504Freenet Liberec, z.s.UnclassifiedIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214886Green hosting s.r.o.UnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS39392SH.cz s.r.o.HostingIPv4 IPv6298
AS6939Hurricane Electric LLCTransitIPv466
AS214886Green hosting s.r.o.UnclassifiedIPv460
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv46
AS20562Broadband Hosting B.V.HostingIPv46
AS24482SG.GSHostingIPv46
AS29504Freenet Liberec, z.s.UnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46

Provenance

Where this comes from

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