asn.dev

Observed topology

AS7656 TWNAP-ADMIN-AS-AP Taiwan Network Access Point

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7656: 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
AS7533Savecom International Inc.UnclassifiedIPv4 IPv6757
AS9676SaveCom Internation Inc.ResidentialIPv4345
AS10133Chief Telecom Inc.UnclassifiedIPv4220
AS24482SG.GSHostingIPv417

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9676SaveCom Internation Inc.ResidentialIPv41,091

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9676SaveCom Internation Inc.ResidentialIPv41,436
AS10133Chief Telecom Inc.UnclassifiedIPv41,022
AS7533Savecom International Inc.UnclassifiedIPv4 IPv6757
AS24482SG.GSHostingIPv4306

Provenance

Where this comes from

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