asn.dev

Observed topology

AS131657 AS-FASTLINE - Hong Da Storage Equipment Co., Ltd.

Unclassified APNIC NSP

Upstreams 9 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 4
Upstream graph Who carries AS131657, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS131657 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS131657: 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.

ASNetworkTypeFamiliesPaths seen
AS199524G-Core Labs S.A.HostingIPv4369
AS13335Cloudflare, Inc.HostingIPv4184
AS18423RAID Networks Co., Ltd.HostingIPv4 IPv6155
AS6939Hurricane Electric LLCTransitIPv4 IPv6143
AS174Cogent Communications, LLCTransitIPv471
AS134823Sky Digital Co., Ltd.ResidentialIPv4 IPv644
AS17408AboveNet Communications TaiwanUnclassifiedIPv435
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

Networks for which AS131657 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS131630Lazco CorporationUnclassifiedIPv49

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS131657 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS18423RAID Networks Co., Ltd.HostingIPv4 IPv6422
AS199524G-Core Labs S.A.HostingIPv4369
AS131630Lazco CorporationUnclassifiedIPv4347
AS13335Cloudflare, Inc.HostingIPv4184
AS174Cogent Communications, LLCTransitIPv4151
AS6939Hurricane Electric LLCTransitIPv4 IPv6143
AS134823Sky Digital Co., Ltd.ResidentialIPv4 IPv644
AS17408AboveNet Communications TaiwanUnclassifiedIPv435
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.