asn.dev

Observed topology

AS210139 DPT

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210139: 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 IPv6120
AS6939Hurricane Electric LLCTransitIPv4 IPv648
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS20562Broadband Hosting B.V.HostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209795SPC-net s.r.o.UnclassifiedIPv4 IPv6150
AS205535Windyghoul s.r.o.UnclassifiedIPv4 IPv6140

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS39392SH.cz s.r.o.HostingIPv4 IPv6336
AS209795SPC-net s.r.o.UnclassifiedIPv4 IPv6150
AS205535Windyghoul s.r.o.UnclassifiedIPv4 IPv6140
AS6939Hurricane Electric LLCTransitIPv4 IPv699
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv68
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv68
AS20562Broadband Hosting B.V.HostingIPv46

Provenance

Where this comes from

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