asn.dev

Observed topology

AS25234 ACTIVE24-AS www.active24.cz

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25234: 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
AS199803ComSource s.r.o.HostingIPv4146
AS46475Limestone Networks, Inc.HostingIPv4 IPv6129
AS6939Hurricane Electric LLCTransitIPv665
AS58003Planeetta Internet OyUnclassifiedIPv4 IPv628
AS29208Quantcom, a.s.UnclassifiedIPv424
AS41528Loopia ABUnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv66
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv66
AS51013WebSupport s.r.o.HostingIPv4 IPv65
AS8218Zayo Infrastructure France SAUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39570Loopia ABHostingIPv4 IPv637

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS199803ComSource s.r.o.HostingIPv4 IPv6178
AS46475Limestone Networks, Inc.HostingIPv4 IPv6129
AS6939Hurricane Electric LLCTransitIPv665
AS39570Loopia ABHostingIPv4 IPv637
AS29208Quantcom, a.s.UnclassifiedIPv4 IPv629
AS58003Planeetta Internet OyUnclassifiedIPv4 IPv628
AS41528Loopia ABUnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv66
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv66
AS51013WebSupport s.r.o.HostingIPv4 IPv65

All 11 adjacent →

Provenance

Where this comes from

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