asn.dev

Observed topology

AS139628 MEGATRUENET-AS-AP Mega Truenet Communication Co., Ltd.

Residential APNIC

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS139628: 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
AS38235ANGKOR DATA COMMUNICATIONResidentialIPv42,385
AS1299Arelion Sweden ABTransitIPv4676
AS55329Telcotech Ltd.UnclassifiedIPv4662
AS2914NTT America, Inc.TransitIPv4494
AS3491PCCW Global (HK) Ltd.TransitIPv4426
AS24482SG.GSHostingIPv478
AS37989DCS1 Pte. Ltd.HostingIPv478
AS38001NewMedia Express Pte LtdHostingIPv478
AS6939Hurricane Electric LLCTransitIPv449
AS58453China Mobile International LimitedUnclassifiedIPv411

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS147023ESURFING TECHNOLOGY CO.LTDUnclassifiedIPv4110
AS147056WOWNOWUnclassifiedIPv449
AS142643BRAVO M LIMITEDUnclassifiedIPv48

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS38235ANGKOR DATA COMMUNICATIONResidentialIPv42,385
AS1299Arelion Sweden ABTransitIPv4676
AS55329Telcotech Ltd.UnclassifiedIPv4662
AS2914NTT America, Inc.TransitIPv4534
AS3491PCCW Global (HK) Ltd.TransitIPv4490
AS147023ESURFING TECHNOLOGY CO.LTDUnclassifiedIPv4110
AS37989DCS1 Pte. Ltd.HostingIPv486
AS38001NewMedia Express Pte LtdHostingIPv485
AS24482SG.GSHostingIPv479
AS6939Hurricane Electric LLCTransitIPv463

All 15 adjacent →

Provenance

Where this comes from

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