Observed topology

AS139620 MTNPCL-AS-AP - MYANMAR TELECOMMUNICATION NETWORK PUBLIC COMPANY LIMITED

Unclassified APNIC NSP

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

Upstream graph Who carries AS139620, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS139620 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS139620: 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.

AS	Network	Type	Families	Paths seen
AS4651	National Telecom Public Company Limited	Unclassified	IPv4 IPv6	100
AS38082	True International Gateway Co., Ltd.	Unclassified	IPv4	60

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS139692	CHEN GUANG COMPANY LIMITED	Unclassified	IPv4	116
AS154481	Tachileik Jade Dragon Company Limited	Unclassified	IPv4 IPv6	80
AS139595	HTIN HTIN NETWORK COMPANY LIMITED	Unclassified	IPv4	64
AS139719	Yar Chang Company Limited	Unclassified	IPv4	27

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4651	National Telecom Public Company Limited	Unclassified	IPv4 IPv6	307
AS38082	True International Gateway Co., Ltd.	Unclassified	IPv4	203
AS139692	CHEN GUANG COMPANY LIMITED	Unclassified	IPv4	116
AS154481	Tachileik Jade Dragon Company Limited	Unclassified	IPv4 IPv6	80
AS139595	HTIN HTIN NETWORK COMPANY LIMITED	Unclassified	IPv4	64
AS151482	MKTN ENGINEERING GROUP COMPANY LIMITED	Unclassified	IPv4	63
AS139719	Yar Chang Company Limited	Unclassified	IPv4	27

Provenance

Where this comes from

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