Observed topology

AS47200 NIX.CZ z.s.p.o.

Unclassified RIPE

Upstreams 0 carry this network

Downstreams 8 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

Upstream graph Who carries AS47200, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS47200 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47200: 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 AS47200 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS16019	Vodafone Czech Republic a.s.	Unclassified	IPv4	44
AS43709	SilesNet s.r.o.	Residential	IPv4	6
AS50698	TETA s.r.o.	Residential	IPv4	6
AS42841	ANTIK Telecom s.r.o	Residential	IPv4	4
AS15935	ha-vel internet s.r.o.	Unclassified	IPv4	3
AS21430	WIA spol. s.r.o.	Unclassified	IPv4	1
AS61241	DONAU INFORMATIK s.r.o.	Unclassified	IPv4	1
AS209719	Ministerstvo Obrany	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS23764	CTGNet	Unclassified	IPv4	79
AS16019	Vodafone Czech Republic a.s.	Unclassified	IPv4	48
AS8778	Slovanet a.s.	Residential	IPv4	8
AS43709	SilesNet s.r.o.	Residential	IPv4	6
AS50698	TETA s.r.o.	Residential	IPv4	6
AS15935	ha-vel internet s.r.o.	Unclassified	IPv4	4
AS42841	ANTIK Telecom s.r.o	Residential	IPv4	4
AS21430	WIA spol. s.r.o.	Unclassified	IPv4	1
AS61241	DONAU INFORMATIK s.r.o.	Unclassified	IPv4	1
AS209719	Ministerstvo Obrany	Unclassified	IPv4	1

Provenance

Where this comes from

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