asn.dev

Observed topology

AS38136 AKARI-NETWORKS-AS-AP Akari Networks

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38136: 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
AS983Akari Networks LLCHostingIPv4 IPv65,504
AS4134No.31,Jin-rong StreetResidentialIPv466
AS9002RETN LimitedUnclassifiedIPv4 IPv652
AS50131Spartan Host LtdUnclassifiedIPv446
AS6939Hurricane Electric LLCTransitIPv4 IPv645
AS3303Swisscom (Schweiz) AGResidentialIPv42
AS24482SG.GSHostingIPv61
AS394256Tech Futures Interactive Inc.UnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152911SY ICTHostingIPv637
AS35251NetLab GlobalHostingIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS983Akari Networks LLCHostingIPv4 IPv65,504
AS6939Hurricane Electric LLCTransitIPv4 IPv680
AS4134No.31,Jin-rong StreetResidentialIPv466
AS9002RETN LimitedUnclassifiedIPv4 IPv652
AS50131Spartan Host LtdUnclassifiedIPv446
AS152911SY ICTHostingIPv637
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv63
AS24482SG.GSHostingIPv62
AS394256Tech Futures Interactive Inc.UnclassifiedIPv62
AS35251NetLab GlobalHostingIPv61

Provenance

Where this comes from

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