asn.dev

Internet exchange

Myanmar Internet Exchange - Yangon

active Yangon, Myanmar RGN

Recorded members 28 addresses on file
Connected ports 12 across all participants
Peak traffic 275 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Yangon, Myanmar
Region
Asia-Pacific
Airport code
RGN
Status
Active
PCH record updated
2026-08-08

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
103.103.194.0/24IPv4Active1
2001:df3:1300::/64IPv6Active12

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

28 shown

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS21859Zenlayer Inc2001:df3:1300::1859:79Selective
AS20940Akamai International B.V.2001:df3:1300::940:25Open
AS199524G-Core Labs S.A.2001:df3:1300::9524:63Selective
AS199524G-Core Labs S.A.103.103.194.63Selective
AS54994Meteverse Limited.2001:df3:1300::4994:7Open
AS139341ACE2001:df3:1300::9341:44Open
AS42WoodyNet, Inc.2001:df3:1300::42:33Open
AS138915Kaopu Cloud HK Limited2001:df3:1300::8915:39Open
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)2001:df3:1300::5152:8Open
AS3856Packet Clearing House, Inc.2001:df3:1300::3856:34Open
AS131322Yatanarpon Teleport Company Limited2001:df3:1300::1322:15Open
AS150692Golden Dragon 20002001:df3:1300::692:43Open
AS137955Myanmar Internet Exchange2001:df3:1300::7955:3Open
AS135371Fortune Broadband2001:df3:1300::5371:16Open
AS132060Hanthar Net2001:df3:1300::2060:54Open
AS135405WELINK2001:df3:1300::13:5405:69Open
AS151965Hepta Alliance Technology Group2001:df3:1300::4484:49Open
AS151965Hepta Alliance Technology Group2001:df3:1300::1965:49
AS152447My Mandalay Company Limited2001:df3:1300::2447:72Open
AS136229Treasure Chindwin Land Co.,Ltd2001:df3:1300::6229:41Open
AS137259i-Link2001:df3:1300::7259:67Open
AS138167TrueNET2001:df3:1300::8167:48Open
AS132344SEANET2001:df3:1300::2344:12Open
AS134484Ultra Net2001:df3:1300::4484:50Open
AS136210IT Spectrum Company Limited2001:df3:1300::6210:36Selective
AS151826Fast Speed2001:df3:1300::1826:68Open
AS9654MYANMAR INET EXCH ASSOC INC.2001:df3:1300::9654:1
AS9654MYANMAR INET EXCH ASSOC INC.2001:df3:1300::9654:2

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.