asn.dev

Observed topology

AS63897 VOCOM-TW vocom international telecom

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS63897: 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
AS9002RETN LimitedUnclassifiedIPv4335
AS45250Vocom International Telecommunications AP AreaHostingIPv4 IPv6243
AS4780Digital United Inc.ResidentialIPv4133
AS24482SG.GSHostingIPv410
AS10133Chief Telecom Inc.UnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135391AOFEI DATA INTERNATIONAL COMPANY LIMITEDHostingIPv4120
AS153891CloudSIM Corporation Ltd.UnclassifiedIPv459
AS45250Vocom International Telecommunications AP AreaHostingIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4532
AS45250Vocom International Telecommunications AP AreaHostingIPv4 IPv6347
AS4780Digital United Inc.ResidentialIPv4200
AS135391AOFEI DATA INTERNATIONAL COMPANY LIMITEDHostingIPv4120
AS153891CloudSIM Corporation Ltd.UnclassifiedIPv459
AS24482SG.GSHostingIPv415
AS10133Chief Telecom Inc.UnclassifiedIPv49

Provenance

Where this comes from

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