Observed topology
AS138195 MOACKCOLTD-AS-AP - MOACK.Co.LTD
Unclassified DROP-listed space ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS138195: 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 |
|---|---|---|---|---|
| AS3786 | LG DACOM Corporation | Unclassified | IPv4 | 6,921 |
| AS138415 | Yancy Limited | Unclassified | IPv4 | 1,799 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 148 |
| AS150684 | JINX CO., LIMITED | Unclassified | IPv4 | 134 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 121 |
| AS9848 | SEJONG NETWORKS | Residential | IPv4 | 74 |
| AS4670 | Shinbiro | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS138195 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS205960 | HDTIDC LIMITED | Unclassified | IPv4 | 1,400 |
| AS399195 | PEG TECH INC | Unclassified | IPv4 | 805 |
| AS9848 | SEJONG NETWORKS | Residential | IPv4 | 720 |
| AS136209 | CyberForest LLC. | Unclassified | IPv4 | 460 |
| AS216047 | INTECLOUD CDNK LTD | Unclassified | IPv4 | 355 |
| AS58931 | 24.hk global BGP | Unclassified | IPv4 | 183 |
| AS136897 | Enjoyvc Cloud Group Limited. | Hosting | IPv4 | 107 |
| AS134835 | Starry Network Limited | Unclassified | IPv4 IPv6 | 91 |
| AS139648 | PacketStream Korea | Hosting | IPv4 | 76 |
| AS138415 | Yancy Limited | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS138195 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3786 | LG DACOM Corporation | Unclassified | IPv4 | 7,789 |
| AS138415 | Yancy Limited | Unclassified | IPv4 | 5,174 |
| AS150684 | JINX CO., LIMITED | Unclassified | IPv4 IPv6 | 2,233 |
| AS398704 | STACKS INC | Unclassified | IPv4 | 1,633 |
| AS205960 | HDTIDC LIMITED | Unclassified | IPv4 | 1,400 |
| AS399195 | PEG TECH INC | Unclassified | IPv4 | 805 |
| AS9848 | SEJONG NETWORKS | Residential | IPv4 | 799 |
| AS136209 | CyberForest LLC. | Unclassified | IPv4 | 460 |
| AS216047 | INTECLOUD CDNK LTD | Unclassified | IPv4 | 355 |
| AS58931 | 24.hk global BGP | Unclassified | IPv4 | 183 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.