Observed topology
AS58461 CT-HangZhou-IDC - No.288,Fu-chun Road
Hosting APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS58461: 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 |
|---|---|---|---|---|
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 | 20,489 |
Transit
Downstream networks
Networks for which AS58461 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS37963 | Hangzhou Alibaba Advertising Co.,Ltd. | Hosting | IPv4 IPv6 | 4,893 |
| AS59037 | Zhejiang Ruili Information Technology Co., Ltd | Unclassified | IPv4 | 1,556 |
| AS45062 | NetEase Building No.16 Ke Yun Road, | Unclassified | IPv4 IPv6 | 1,174 |
| AS55991 | CNNIC ASN block | Unclassified | IPv4 | 1,074 |
| AS21856 | Nokia of America Corporation | Unclassified | IPv4 IPv6 | 148 |
| AS24406 | China Internet Network Infomation Center | Unclassified | IPv6 | 32 |
Adjacency
Adjacent networks
Every AS seen directly next to AS58461 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 IPv6 | 29,366 |
| AS37963 | Hangzhou Alibaba Advertising Co.,Ltd. | Hosting | IPv4 IPv6 | 4,893 |
| AS59037 | Zhejiang Ruili Information Technology Co., Ltd | Unclassified | IPv4 | 1,556 |
| AS45062 | NetEase Building No.16 Ke Yun Road, | Unclassified | IPv4 IPv6 | 1,174 |
| AS55991 | CNNIC ASN block | Unclassified | IPv4 | 1,074 |
| AS21856 | Nokia of America Corporation | Unclassified | IPv4 IPv6 | 148 |
| AS24406 | China Internet Network Infomation Center | Unclassified | IPv6 | 32 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.