asn.dev

Observed topology

AS38738 LCS-AS-VN L.C.S Company.,ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38738: 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
AS7552Viettel GroupMobileIPv4334
AS45896Mobifone Global JSCUnclassifiedIPv4 IPv6225
AS38731Vietel - CHT Compamy LtdHostingIPv458

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135926Phu Nhuan Jewelry Joint Stock CompanyUnclassifiedIPv4275
AS13592516 Au Co, Tan Son Nhi Ward, Tan Phu District, Ho Chi Minh city (EVNSPC Building)UnclassifiedIPv4115
AS135943TRUONG MINH THINH TECHNOLOGY JOINT STOCK COMPANYUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45896Mobifone Global JSCUnclassifiedIPv4 IPv6657
AS7552Viettel GroupMobileIPv4480
AS135926Phu Nhuan Jewelry Joint Stock CompanyUnclassifiedIPv4275
AS135943TRUONG MINH THINH TECHNOLOGY JOINT STOCK COMPANYUnclassifiedIPv4188
AS13592516 Au Co, Tan Son Nhi Ward, Tan Phu District, Ho Chi Minh city (EVNSPC Building)UnclassifiedIPv4115
AS38731Vietel - CHT Compamy LtdHostingIPv458

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.