Observed topology
AS133385 ATOMMYANMAR-AS-AP Atom Myanmar Limited
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS133385: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,323 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 807 |
| AS4229 | Zenlayer Inc | Hosting | IPv4 IPv6 | 626 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 75 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 | 30 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 28 |
| AS132132 | MyRepublic Ltd. | Residential | IPv4 | 15 |
Transit
Downstream networks
Networks for which AS133385 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS136442 | Ocean Wave Communication Co., Ltd | Residential | IPv4 | 594 |
| AS135405 | WELINK | Unclassified | IPv4 | 272 |
| AS135427 | Myanmar Network Company Limited | Unclassified | IPv4 | 237 |
| AS134840 | Myanmar Country Co., Ltd. | Residential | IPv4 IPv6 | 129 |
| AS150797 | GIGA-NET | Unclassified | IPv4 IPv6 | 129 |
| AS136780 | MYANMAR INFORMATION HIGHWAY LIMITED | Residential | IPv4 | 119 |
| AS136480 | Myanmar Unilink Communication Company Limited | Unclassified | IPv4 | 118 |
| AS152191 | YOUNIQUE INFO TECH CO., LTD | Unclassified | IPv4 | 116 |
| AS150812 | Myanmar Fortune Global Company Limited | Unclassified | IPv4 | 115 |
| AS153998 | Myanmar Citizens Bank Public Company Limited | Unclassified | IPv4 | 106 |
Adjacency
Adjacent networks
Every AS seen directly next to AS133385 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,409 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,281 |
| AS4229 | Zenlayer Inc | Hosting | IPv4 IPv6 | 1,232 |
| AS131322 | Yatanarpon Teleport Company Limited | Unclassified | IPv4 | 649 |
| AS136442 | Ocean Wave Communication Co., Ltd | Residential | IPv4 | 594 |
| AS135405 | WELINK | Unclassified | IPv4 | 272 |
| AS136205 | LINN IT Solution Co., Ltd | Unclassified | IPv4 IPv6 | 269 |
| AS135427 | Myanmar Network Company Limited | Unclassified | IPv4 | 237 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 148 |
| AS134840 | Myanmar Country Co., Ltd. | Residential | IPv4 IPv6 | 129 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.