asn.dev

Observed topology

AS46824 NAMECRANE

Hosting ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS46824: 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 IPv6262
AS35133Eranium B.V.HostingIPv4 IPv646
AS32097WholeSale Internet, Inc.HostingIPv445
AS53667FranTech SolutionsHostingIPv636
AS174Cogent Communications, LLCTransitIPv4 IPv633
AS50304Blix Solutions ASUnclassifiedIPv42
AS12859BIT BVHostingIPv41
AS20764CJSC RASCOMUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS34927iFog GmbHHostingIPv41

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS965Webhosting Holdings LLCUnclassifiedIPv4 IPv6383
AS46978Bytesize Internet LLCUnclassifiedIPv4 IPv694
AS401727Aurora Development LLCUnclassifiedIPv637

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6540
AS965Webhosting Holdings LLCUnclassifiedIPv4 IPv6383
AS35133Eranium B.V.HostingIPv4 IPv6186
AS46978Bytesize Internet LLCUnclassifiedIPv4 IPv694
AS32097WholeSale Internet, Inc.HostingIPv490
AS174Cogent Communications, LLCTransitIPv4 IPv662
AS401727Aurora Development LLCUnclassifiedIPv637
AS53667FranTech SolutionsHostingIPv636
AS50304Blix Solutions ASUnclassifiedIPv49
AS24482SG.GSHostingIPv45

All 14 adjacent →

Provenance

Where this comes from

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