asn.dev

Observed topology

AS25424 INEXT-CZ CEZNET s.r.o.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25424: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6134
AS6939Hurricane Electric LLCTransitIPv4 IPv6130
AS1299Arelion Sweden ABTransitIPv4 IPv6124
AS39791Telco Pro Services, a. s.UnclassifiedIPv479
AS24482SG.GSHostingIPv4 IPv69
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv69

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6740CEZNET s.r.o.ResidentialIPv4236
AS211137ISP Services spol. s.r.o.,UnclassifiedIPv459
AS49580Monet +, a.s.UnclassifiedIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6740CEZNET s.r.o.ResidentialIPv4236
AS174Cogent Communications, LLCTransitIPv4 IPv6220
AS1299Arelion Sweden ABTransitIPv4 IPv6220
AS6939Hurricane Electric LLCTransitIPv4 IPv6180
AS39791Telco Pro Services, a. s.UnclassifiedIPv4140
AS211137ISP Services spol. s.r.o.,UnclassifiedIPv459
AS24482SG.GSHostingIPv4 IPv614
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv614
AS49580Monet +, a.s.UnclassifiedIPv48

Provenance

Where this comes from

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