asn.dev

Observed topology

AS16019 VODAFONE-CZ-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS1273IDDQD-ASBusinessIPv4 IPv62,212
AS6939Hurricane Electric LLCTransitIPv4 IPv61,288
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv6107
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6107
AS24482SG.GSHostingIPv4 IPv6107
AS33891Core-Backbone GmbHHostingIPv490
AS47232ISP Alliance a.s.ResidentialIPv489
AS6461Zayo BandwidthTransitIPv4 IPv669
AS47200NIX.CZ z.s.p.o.UnclassifiedIPv444
AS5610O2 Czech Republic, a.s.UnclassifiedIPv41

Transit

Downstream networks

All 91

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

ASNetworkTypeFamiliesPaths seen
AS204666Jiri TlapakUnclassifiedIPv4 IPv62,236
AS35592Coolhousing s.r.o.HostingIPv4 IPv61,239
AS204383SPCom s.r.o.UnclassifiedIPv4 IPv61,173
AS201730Cloud4com s.r.o.UnclassifiedIPv4 IPv61,157
AS2571DHL Information Services (Europe) s.r.oUnclassifiedIPv4 IPv6527
AS52154mjanik.net s.r.o.UnclassifiedIPv4474
AS41030Jaroslav NovotnyUnclassifiedIPv4420
AS43773PE Konstantin Vladimirovich KravchenkoUnclassifiedIPv4420
AS47269Core4Net, s.r.o.UnclassifiedIPv4 IPv6333
AS205619Jiri ChalabalaUnclassifiedIPv4 IPv6275

Adjacency

Adjacent networks

All 103

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

ASNetworkTypeFamiliesPaths seen
AS1273IDDQD-ASBusinessIPv4 IPv613,475
AS6939Hurricane Electric LLCTransitIPv4 IPv63,909
AS204666Jiri TlapakUnclassifiedIPv4 IPv62,340
AS35592Coolhousing s.r.o.HostingIPv4 IPv61,307
AS204383SPCom s.r.o.UnclassifiedIPv4 IPv61,266
AS201730Cloud4com s.r.o.UnclassifiedIPv4 IPv61,157
AS197451Brno University of TechnologyEducationIPv4 IPv6712
AS2571DHL Information Services (Europe) s.r.oUnclassifiedIPv4 IPv6527
AS52154mjanik.net s.r.o.UnclassifiedIPv4 IPv6507
AS47232ISP Alliance a.s.ResidentialIPv4499

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.