asn.dev

Observed topology

AS203072 DomaTV s.r.o.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203072: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39906CoProSys a.s.UnclassifiedIPv4 IPv6725
AS41088"N_SYS s.r.o."UnclassifiedIPv4 IPv6185
AS47131PH, spol. s r. o.UnclassifiedIPv4128

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS39906CoProSys a.s.UnclassifiedIPv4 IPv6785
AS39392SH.cz s.r.o.HostingIPv4 IPv6618
AS6939Hurricane Electric LLCTransitIPv4 IPv6228
AS41088"N_SYS s.r.o."UnclassifiedIPv4 IPv6185
AS16019Vodafone Czech Republic a.s.UnclassifiedIPv4 IPv6140
AS47131PH, spol. s r. o.UnclassifiedIPv4128
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv620
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv620
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv619

All 12 adjacent →

Provenance

Where this comes from

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