Observed topology
AS152586 KUROIT-AS-AP - Kuroit
Unclassified APNIC Enterprise
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 529 |
| AS25369 | Hydra Communications Ltd | Hosting | IPv4 IPv6 | 445 |
| AS401665 | HostBilby Inc. | Hosting | IPv4 IPv6 | 362 |
| AS26548 | PureVoltage Hosting Inc. | Hosting | IPv4 IPv6 | 327 |
| AS3170 | VeloxServ Communications Ltd | Hosting | IPv4 | 180 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 154 |
| AS26042 | FiberState, LLC | Hosting | IPv4 IPv6 | 102 |
| AS61138 | Zappie Host LLC | Unclassified | IPv4 IPv6 | 96 |
Transit
Downstream networks
Networks for which AS152586 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS210495 | WENIUM LTD | Unclassified | IPv4 | 241 |
Adjacency
Adjacent networks
Every AS seen directly next to AS152586 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 590 |
| AS25369 | Hydra Communications Ltd | Hosting | IPv4 IPv6 | 445 |
| AS26548 | PureVoltage Hosting Inc. | Hosting | IPv4 IPv6 | 385 |
| AS401665 | HostBilby Inc. | Hosting | IPv4 IPv6 | 362 |
| AS3170 | VeloxServ Communications Ltd | Hosting | IPv4 | 302 |
| AS210495 | WENIUM LTD | Unclassified | IPv4 | 241 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 154 |
| AS26042 | FiberState, LLC | Hosting | IPv4 IPv6 | 102 |
| AS61138 | Zappie Host LLC | Unclassified | IPv4 IPv6 | 96 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.