asn.dev

Observed topology

AS29134 IGNUM-AS Czech Republic

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29134: 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
AS35236UVT Internet s.r.o.UnclassifiedIPv4 IPv6603
AS6939Hurricane Electric LLCTransitIPv4188
AS47232ISP Alliance a.s.ResidentialIPv4 IPv684
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv627
AS6855Slovak Telekom, a.s.MobileIPv418
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv617
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60592Gransy s.r.o.HostingIPv4236
AS200806BOHEMIA ENERGY entity s.r.o.UnclassifiedIPv4118
AS51278Webglobe, s.r.o.UnclassifiedIPv4 IPv695

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS35236UVT Internet s.r.o.UnclassifiedIPv4 IPv6897
AS6939Hurricane Electric LLCTransitIPv4266
AS60592Gransy s.r.o.HostingIPv4236
AS47232ISP Alliance a.s.ResidentialIPv4 IPv6120
AS200806BOHEMIA ENERGY entity s.r.o.UnclassifiedIPv4118
AS51278Webglobe, s.r.o.UnclassifiedIPv4 IPv695
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv636
AS24482SG.GSHostingIPv4 IPv635
AS6855Slovak Telekom, a.s.MobileIPv428
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv625

All 11 adjacent →

Provenance

Where this comes from

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