Observed topology
AS204844 NCSE-NETWORK-GLOBAL
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS204844: 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 | 414 |
| AS134823 | Sky Digital Co., Ltd. | Residential | IPv4 IPv6 | 106 |
| AS32595 | Liberally Network, LLC | Residential | IPv4 | 96 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 73 |
| AS20473 | The Constant Company, LLC | Hosting | IPv6 | 32 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 17 |
| AS38855 | Taiwan Digital Streaming Co. | Unclassified | IPv4 IPv6 | 17 |
| AS17408 | AboveNet Communications Taiwan | Unclassified | IPv4 IPv6 | 9 |
Transit
Downstream networks
Networks for which AS204844 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS131630 | Lazco Corporation | Unclassified | IPv4 | 269 |
| AS214841 | RUI PIN LAI | Unclassified | IPv6 | 185 |
| AS152616 | BHIS Ltd. | Unclassified | IPv4 IPv6 | 132 |
| AS205592 | HUANG CHI-HAN | Unclassified | IPv6 | 76 |
| AS207389 | JING-SHIUN-CHEN | Unclassified | IPv6 | 72 |
| AS152615 | Chummy Technology Ltd. | Unclassified | IPv4 | 59 |
| AS216100 | Rui Li | Unclassified | IPv6 | 41 |
| AS201943 | HSIEH HUAN-YU | Unclassified | IPv6 | 37 |
| AS212969 | ChiaChin Tsai | Unclassified | IPv6 | 37 |
| AS215934 | XU JIA QIAN | Unclassified | IPv6 | 35 |
Adjacency
Adjacent networks
Every AS seen directly next to AS204844 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,003 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 401 |
| AS131630 | Lazco Corporation | Unclassified | IPv4 IPv6 | 271 |
| AS214841 | RUI PIN LAI | Unclassified | IPv6 | 185 |
| AS152616 | BHIS Ltd. | Unclassified | IPv4 IPv6 | 132 |
| AS134823 | Sky Digital Co., Ltd. | Residential | IPv4 IPv6 | 124 |
| AS32595 | Liberally Network, LLC | Residential | IPv4 | 96 |
| AS17408 | AboveNet Communications Taiwan | Unclassified | IPv4 IPv6 | 82 |
| AS205592 | HUANG CHI-HAN | Unclassified | IPv6 | 76 |
| AS207389 | JING-SHIUN-CHEN | Unclassified | IPv6 | 72 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.