Observed topology

AS134840 MCCL-AS-AP Myanmar Country Co., Ltd.

Residential APNIC

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134840: 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
AS136168	Campana MYTHIC Co. Ltd.	Unclassified	IPv4 IPv6	1,135
AS136255	Telecom International Myanmar Co., Ltd	Unclassified	IPv4 IPv6	386
AS45558	MYANMA POSTS AND TELECOMMUNICATIONS	Residential	IPv4	242
AS133385	Atom Myanmar Limited	Residential	IPv4 IPv6	129
AS133524	Global Technology Co., Ltd.	Unclassified	IPv4	129

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS24429	Zhejiang Taobao Network Co.,Ltd	Hosting	IPv4	43

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS136168	Campana MYTHIC Co. Ltd.	Unclassified	IPv4 IPv6	1,137
AS136255	Telecom International Myanmar Co., Ltd	Unclassified	IPv4 IPv6	429
AS45558	MYANMA POSTS AND TELECOMMUNICATIONS	Residential	IPv4	244
AS133385	Atom Myanmar Limited	Residential	IPv4 IPv6	129
AS133524	Global Technology Co., Ltd.	Unclassified	IPv4	129
AS24429	Zhejiang Taobao Network Co.,Ltd	Hosting	IPv4	43

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.