asn.dev

Observed topology

AS219499 ZUNGWAICLOUD HK ZUNGWAI CLOUD LIMITED

Unclassified DROP-listed space RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS219499: 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
AS55720Gigabit Hosting Sdn BhdHostingIPv4130
AS150706Hong Kong Zhengxing Technology Co., Ltd.UnclassifiedIPv4 IPv650
AS17476CloudRadium (HK) LimitedResidentialIPv443

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS148996GLOBAL COMMUNICATION NETWORK LIMITEDUnclassifiedIPv4960

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS17476CloudRadium (HK) LimitedResidentialIPv41,003
AS148996GLOBAL COMMUNICATION NETWORK LIMITEDUnclassifiedIPv4960
AS55720Gigabit Hosting Sdn BhdHostingIPv4130
AS150706Hong Kong Zhengxing Technology Co., Ltd.UnclassifiedIPv4 IPv650

Provenance

Where this comes from

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