asn.dev

Observed topology

AS148996 GCNL-AS-AP GLOBAL COMMUNICATION NETWORK LIMITED

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS148996: 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
AS214432Zhilian Technology CO., LTD.UnclassifiedIPv410,178
AS219499HK ZUNGWAI CLOUD LIMITEDUnclassifiedIPv4944
AS134823Sky Digital Co., Ltd.ResidentialIPv4699
AS21859Zenlayer IncHostingIPv4513
AS17497Liasail Global Hongkong LimitedUnclassifiedIPv4464
AS48266Catixs LtdUnclassifiedIPv4232
AS138077PT Abhinawa Sumberdaya AsiaHostingIPv4122
AS138997Eons Data Communications LimitedUnclassifiedIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152179GLOBAL COMMUNICATION NETWORK LIMITEDResidentialIPv4116

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS214432Zhilian Technology CO., LTD.UnclassifiedIPv410,178
AS219499HK ZUNGWAI CLOUD LIMITEDUnclassifiedIPv4944
AS134823Sky Digital Co., Ltd.ResidentialIPv4699
AS21859Zenlayer IncHostingIPv4513
AS17497Liasail Global Hongkong LimitedUnclassifiedIPv4464
AS48266Catixs LtdUnclassifiedIPv4348
AS138077PT Abhinawa Sumberdaya AsiaHostingIPv4122
AS152179GLOBAL COMMUNICATION NETWORK LIMITEDResidentialIPv4116
AS138997Eons Data Communications LimitedUnclassifiedIPv459

Provenance

Where this comes from

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