asn.dev

Observed topology

AS38901 EZECOM-AS-AP EZECOM CO., LTD.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38901: 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
AS55329Telcotech Ltd.UnclassifiedIPv4 IPv67,388
AS23764CTGNetUnclassifiedIPv43,442
AS45474Nexusguard Pte. Ltd.HostingIPv436

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS131178EZECOM CO., LTD.ResidentialIPv4 IPv65,735
AS17976CAMGSM Company LtdUnclassifiedIPv41,444
AS137829LOLC CAMBODIA PLC.UnclassifiedIPv471
AS142296General Department of TaxationUnclassifiedIPv460
AS138580Ministry of Economy and FinanceUnclassifiedIPv455
AS150796DGB BANK PLC.UnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55329Telcotech Ltd.UnclassifiedIPv4 IPv613,060
AS131178EZECOM CO., LTD.ResidentialIPv4 IPv65,735
AS23764CTGNetUnclassifiedIPv45,137
AS17976CAMGSM Company LtdUnclassifiedIPv41,444
AS137829LOLC CAMBODIA PLC.UnclassifiedIPv471
AS142296General Department of TaxationUnclassifiedIPv460
AS138580Ministry of Economy and FinanceUnclassifiedIPv455
AS45474Nexusguard Pte. Ltd.HostingIPv436
AS150796DGB BANK PLC.UnclassifiedIPv42

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.