asn.dev

Observed topology

AS51430 ALTUS AltusHost B.V.

Unclassified RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS51430: 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
AS201789NETOPS B.V.UnclassifiedIPv4 IPv62,335
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv6502
AS9002RETN LimitedUnclassifiedIPv4 IPv6442
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6331
AS174Cogent Communications, LLCTransitIPv4 IPv6218
AS6939Hurricane Electric LLCTransitIPv4 IPv6132
AS24482SG.GSHostingIPv4 IPv618
AS34019Hivane AssociationUnclassifiedIPv4 IPv618
AS58057Securebit AGUnclassifiedIPv4 IPv618
AS34927iFog GmbHHostingIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45839Shinjiru Technology Sdn BhdHostingIPv4183
AS199968IWS NETWORKS LLCUnclassifiedIPv4119
AS136787PacketHub S.A.VPNIPv462
AS61295NETOPS B.V.UnclassifiedIPv461

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS201789NETOPS B.V.UnclassifiedIPv4 IPv62,335
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv6620
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6558
AS9002RETN LimitedUnclassifiedIPv4 IPv6498
AS174Cogent Communications, LLCTransitIPv4 IPv6218
AS45839Shinjiru Technology Sdn BhdHostingIPv4183
AS6939Hurricane Electric LLCTransitIPv4 IPv6146
AS199968IWS NETWORKS LLCUnclassifiedIPv4119
AS136787PacketHub S.A.VPNIPv462
AS61295NETOPS B.V.UnclassifiedIPv461

Provenance

Where this comes from

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