asn.dev

Observed topology

AS38244 VINAGAME-AS-VN - VNG Corporation

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38244: 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
AS45543SaiGon Tourist cable Televition CompanyMobileIPv4 IPv64,472
AS18403FPT Telecom CompanyResidentialIPv4 IPv62,006
AS21859Zenlayer IncHostingIPv41,432
AS131440ZINGPLAY VIETNAM COMPANY LIMITEDUnclassifiedIPv4116
AS45903CMC Telecom Infrastructure CompanyResidentialIPv4 IPv663

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135944VinhNam Commercial informatics service corporationUnclassifiedIPv41,098
AS154105ZALO PLATFORMS COMPANY LIMITEDUnclassifiedIPv4 IPv6282
AS131440ZINGPLAY VIETNAM COMPANY LIMITEDUnclassifiedIPv4260
AS150856VNG DATA CENTER CO., LTDUnclassifiedIPv4 IPv6101

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45543SaiGon Tourist cable Televition CompanyMobileIPv4 IPv65,068
AS18403FPT Telecom CompanyResidentialIPv4 IPv62,951
AS21859Zenlayer IncHostingIPv41,520
AS135944VinhNam Commercial informatics service corporationUnclassifiedIPv41,098
AS131440ZINGPLAY VIETNAM COMPANY LIMITEDUnclassifiedIPv4376
AS154105ZALO PLATFORMS COMPANY LIMITEDUnclassifiedIPv4 IPv6282
AS45903CMC Telecom Infrastructure CompanyResidentialIPv4 IPv6175
AS150856VNG DATA CENTER CO., LTDUnclassifiedIPv4 IPv6101

Provenance

Where this comes from

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