Observed topology
AS16019 VODAFONE-CZ-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS16019: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 2,212 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,288 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 IPv6 | 107 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 IPv6 | 107 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 107 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 90 |
| AS47232 | ISP Alliance a.s. | Residential | IPv4 | 89 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 69 |
| AS47200 | NIX.CZ z.s.p.o. | Unclassified | IPv4 | 44 |
| AS5610 | O2 Czech Republic, a.s. | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS16019 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204666 | Jiri Tlapak | Unclassified | IPv4 IPv6 | 2,236 |
| AS35592 | Coolhousing s.r.o. | Hosting | IPv4 IPv6 | 1,239 |
| AS204383 | SPCom s.r.o. | Unclassified | IPv4 IPv6 | 1,173 |
| AS201730 | Cloud4com s.r.o. | Unclassified | IPv4 IPv6 | 1,157 |
| AS2571 | DHL Information Services (Europe) s.r.o | Unclassified | IPv4 IPv6 | 527 |
| AS52154 | mjanik.net s.r.o. | Unclassified | IPv4 | 474 |
| AS41030 | Jaroslav Novotny | Unclassified | IPv4 | 420 |
| AS43773 | PE Konstantin Vladimirovich Kravchenko | Unclassified | IPv4 | 420 |
| AS47269 | Core4Net, s.r.o. | Unclassified | IPv4 IPv6 | 333 |
| AS205619 | Jiri Chalabala | Unclassified | IPv4 IPv6 | 275 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16019 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 13,475 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,909 |
| AS204666 | Jiri Tlapak | Unclassified | IPv4 IPv6 | 2,340 |
| AS35592 | Coolhousing s.r.o. | Hosting | IPv4 IPv6 | 1,307 |
| AS204383 | SPCom s.r.o. | Unclassified | IPv4 IPv6 | 1,266 |
| AS201730 | Cloud4com s.r.o. | Unclassified | IPv4 IPv6 | 1,157 |
| AS197451 | Brno University of Technology | Education | IPv4 IPv6 | 712 |
| AS2571 | DHL Information Services (Europe) s.r.o | Unclassified | IPv4 IPv6 | 527 |
| AS52154 | mjanik.net s.r.o. | Unclassified | IPv4 IPv6 | 507 |
| AS47232 | ISP Alliance a.s. | Residential | IPv4 | 499 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.