Observed topology
AS18013 ASLINE-AS-AP - ASLINE LIMITED
Hosting APNIC Route Server
Transit
Upstream networks
Networks observed carrying traffic for AS18013: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 412 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 331 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 193 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 121 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 64 |
| AS40065 | CNSERVERS LLC | Hosting | IPv4 | 59 |
| AS10111 | Zeofast Network | Unclassified | IPv4 | 23 |
| AS22427 | GNET INC. | Unclassified | IPv4 | 10 |
| AS23764 | CTGNet | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS18013 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9294 | GNET INC. | Unclassified | IPv4 | 7,035 |
| AS137951 | ASLINE LIMITED | Unclassified | IPv4 | 3,238 |
| AS136970 | YISU CLOUD LTD | Unclassified | IPv4 | 1,026 |
| AS393889 | EightJoy Network LLC | Unclassified | IPv4 | 832 |
| AS976 | CoreNET Inc. | Residential | IPv4 IPv6 | 488 |
| AS38186 | Forewin Telecom Group Limited, ISP at HK | Hosting | IPv4 | 417 |
| AS22160 | INIsmart Technology Ltd. | Unclassified | IPv4 | 413 |
| AS134428 | Edge Cloud Globe Co., Limited | Unclassified | IPv4 | 238 |
| AS138415 | Yancy Limited | Unclassified | IPv4 | 130 |
| AS402246 | INIsmart Technology Ltd. | Unclassified | IPv4 | 130 |
Adjacency
Adjacent networks
Every AS seen directly next to AS18013 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17476 | CloudRadium (HK) Limited | Residential | IPv4 | 7,252 |
| AS9294 | GNET INC. | Unclassified | IPv4 | 7,035 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 5,776 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 4,311 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,493 |
| AS137951 | ASLINE LIMITED | Unclassified | IPv4 | 3,238 |
| AS40779 | VoltNet inc | Unclassified | IPv4 | 2,789 |
| AS136970 | YISU CLOUD LTD | Unclassified | IPv4 | 2,782 |
| AS136826 | PT TITIK TERANG MAKMUR | Unclassified | IPv4 | 1,307 |
| AS976 | CoreNET Inc. | Residential | IPv4 IPv6 | 991 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.