asn.dev

Observed topology

AS152586 KUROIT-AS-AP Kuroit

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152586: 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
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6522
AS25369Hydra Communications LtdHostingIPv4 IPv6439
AS401665HostBilby Inc.HostingIPv4 IPv6362
AS26548PureVoltage Hosting Inc.HostingIPv4 IPv6323
AS3170VeloxServ Communications LtdHostingIPv4180
AS9498BHARTI Airtel Ltd.MobileIPv4116
AS26042FiberState, LLCHostingIPv4 IPv6102
AS61138Zappie Host LLCUnclassifiedIPv4 IPv694
AS9730Bharti Telesonic LtdUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210495WENIUM LTDUnclassifiedIPv4238

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6583
AS25369Hydra Communications LtdHostingIPv4 IPv6439
AS26548PureVoltage Hosting Inc.HostingIPv4 IPv6380
AS401665HostBilby Inc.HostingIPv4 IPv6362
AS3170VeloxServ Communications LtdHostingIPv4300
AS210495WENIUM LTDUnclassifiedIPv4238
AS9498BHARTI Airtel Ltd.MobileIPv4116
AS26042FiberState, LLCHostingIPv4 IPv6102
AS61138Zappie Host LLCUnclassifiedIPv4 IPv694
AS9730Bharti Telesonic LtdUnclassifiedIPv41

Provenance

Where this comes from

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