Observed topology

AS151482 MKTN-AS-AP MKTN ENGINEERING GROUP COMPANY LIMITED

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS151482: 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
AS45558	MYANMA POSTS AND TELECOMMUNICATIONS	Residential	IPv4	64
AS133385	Atom Myanmar Limited	Residential	IPv4	12

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS139058	TCL Net	Unclassified	IPv4	195

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS139058	TCL Net	Unclassified	IPv4	195
AS133524	Global Technology Co., Ltd.	Unclassified	IPv4	65
AS139620	MYANMAR TELECOMMUNICATION NETWORK PUBLIC COMPANY LIMITED	Unclassified	IPv4	65
AS151210	NEXGENET COMPANY LIMITED	Unclassified	IPv4	65
AS45558	MYANMA POSTS AND TELECOMMUNICATIONS	Residential	IPv4	64
AS133385	Atom Myanmar Limited	Residential	IPv4	12

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.