asn.dev

Observed topology

AS12570 ITSELF O2 Czech Republic, a.s.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12570: 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
AS16246O2 Czech Republic, a.s.UnclassifiedIPv4 IPv6721

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213354Iryna OliinykUnclassifiedIPv4 IPv6381
AS51424Jiri SperlUnclassifiedIPv4240
AS204886Metropolitni sit Humpolec spol. s r.o.UnclassifiedIPv4 IPv690
AS196815LAN servis s.r.o.UnclassifiedIPv460
AS198620Bralu Jurjanu biedribaUnclassifiedIPv459
AS211334MASTER IT Technologies, a.s.UnclassifiedIPv459
AS25192CZ.NIC, z.s.p.o.UnclassifiedIPv443
AS202979NGA Services, spol. s r.o.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS16246O2 Czech Republic, a.s.UnclassifiedIPv4 IPv61,655
AS213354Iryna OliinykUnclassifiedIPv4 IPv6381
AS51424Jiri SperlUnclassifiedIPv4240
AS204886Metropolitni sit Humpolec spol. s r.o.UnclassifiedIPv4 IPv690
AS196815LAN servis s.r.o.UnclassifiedIPv460
AS198620Bralu Jurjanu biedribaUnclassifiedIPv459
AS211334MASTER IT Technologies, a.s.UnclassifiedIPv459
AS25192CZ.NIC, z.s.p.o.UnclassifiedIPv443
AS47232ISP Alliance a.s.ResidentialIPv41
AS202979NGA Services, spol. s r.o.UnclassifiedIPv41

Provenance

Where this comes from

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