asn.dev

Observed topology

AS56430 CHROOT Chroot Network SRL

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS56430: 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
AS12310iNES GROUP SRLUnclassifiedIPv4468
AS6663Euroweb Romania S.R.L.UnclassifiedIPv4 IPv6384
AS6939Hurricane Electric LLCTransitIPv6184
AS9009M247 Europe SRLHostingIPv4 IPv625
AS24482SG.GSHostingIPv4 IPv619

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57640Chroot Network SRLUnclassifiedIPv636
AS9053VSHosting s.r.o.HostingIPv624

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12310iNES GROUP SRLUnclassifiedIPv4 IPv6469
AS6663Euroweb Romania S.R.L.UnclassifiedIPv4 IPv6384
AS6939Hurricane Electric LLCTransitIPv6240
AS57640Chroot Network SRLUnclassifiedIPv636
AS9009M247 Europe SRLHostingIPv4 IPv627
AS9053VSHosting s.r.o.HostingIPv624
AS24482SG.GSHostingIPv4 IPv620

Provenance

Where this comes from

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