Observed topology
AS149522 ONECUBITCOLTD-AS-AP - OneCubit Co., Ltd.
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS149522: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 179 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 146 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 129 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 98 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 68 |
| AS60068 | Datacamp Limited | Hosting | IPv4 | 12 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS9957 | KINX | Hosting | IPv4 IPv6 | 3 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 3 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS149522 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS132088 | Wind Cloud Network Technology Co Ltd | Hosting | IPv6 | 642 |
| AS204091 | Rivulet Wireless Inc. | Unclassified | IPv6 | 175 |
| AS150414 | OneCubit Co., Ltd. | Unclassified | IPv6 | 67 |
| AS1064 | Rivulet Wireless Inc. | Unclassified | IPv4 | 57 |
| AS150314 | Rivulet Networks | Unclassified | IPv6 | 36 |
| AS138986 | INAP Japan Tokyo Shiohama DC | Unclassified | IPv6 | 35 |
Adjacency
Adjacent networks
Every AS seen directly next to AS149522 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS132088 | Wind Cloud Network Technology Co Ltd | Hosting | IPv6 | 642 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 536 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 419 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 234 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 204 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 179 |
| AS204091 | Rivulet Wireless Inc. | Unclassified | IPv6 | 175 |
| AS150414 | OneCubit Co., Ltd. | Unclassified | IPv6 | 67 |
| AS1064 | Rivulet Wireless Inc. | Unclassified | IPv4 | 57 |
| AS150314 | Rivulet Networks | Unclassified | IPv6 | 36 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.