asn.dev

Observed topology

AS924 CLOUDIE - Cloudie Networks LLC

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS924: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6201
AS61138Zappie Host LLCUnclassifiedIPv672
AS400587Ryamer, LLCHostingIPv4 IPv619
AS34927iFog GmbHHostingIPv64
AS612184b42 UGUnclassifiedIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63279XKEYHostingIPv4 IPv6377
AS393435Lyle ResearchUnclassifiedIPv4 IPv6224
AS54681Aubrey RoseResidentialIPv4 IPv6146
AS61138Zappie Host LLCUnclassifiedIPv462
AS205848Dominik PohlHostingIPv636
AS44570Xodo Technology, LLC.UnclassifiedIPv64
AS54148Dynamic Quantum NetworksUnclassifiedIPv61

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,025
AS63279XKEYHostingIPv4 IPv6377
AS393435Lyle ResearchUnclassifiedIPv4 IPv6224
AS54681Aubrey RoseResidentialIPv4 IPv6146
AS61138Zappie Host LLCUnclassifiedIPv4 IPv6134
AS400587Ryamer, LLCHostingIPv4 IPv645
AS205848Dominik PohlHostingIPv636
AS34927iFog GmbHHostingIPv64
AS44570Xodo Technology, LLC.UnclassifiedIPv64
AS612184b42 UGUnclassifiedIPv4 IPv64

All 11 adjacent →

Provenance

Where this comes from

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