Network · data from 2026-11-12
AS9988 Myanma Posts and Telecommunications (MPT)
Registry name: MPT-AP - Myanma Posts and Telecommunications, MM · PeeringDB
65IPv4 routes
95.4% RPKI valid · 98.5% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
0 origin · 1 maxLength
2No ROA
1 with no route object for this origin
6Low visibility
seen by under 10% of full-table peers
65Route objects not announced
registered with origin AS9988, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS9988, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 203.81.71.0/24 | Invalid: maxLength | Nonecovered by 203.81.68.0/22 | 10 1%low visibility |
| 103.206.173.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.47.184.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 43.224.40.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 43.224.40.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 43.224.41.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 43.224.42.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 43.224.42.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.41.100.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.41.104.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.41.112.0/20 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.112.176.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.112.177.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.112.178.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.112.179.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.25.12.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.52.12.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.52.14.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 136.228.160.0/20 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.160.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.160.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.164.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.164.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 136.228.165.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.166.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.167.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.168.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.172.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 136.228.172.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.173.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 136.228.174.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 136.228.174.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 136.228.175.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.81.64.0/19 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.81.64.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.81.64.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.81.68.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.81.72.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.81.80.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.81.84.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.81.85.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.81.88.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.81.88.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.81.92.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.41.104.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.41.106.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 136.228.162.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 136.228.163.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 136.228.168.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 136.228.169.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 136.228.170.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 136.228.171.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.81.72.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 45.41.105.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 45.41.111.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 45.112.176.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 136.228.161.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 45.41.108.0/22 | Valid | RIR databaseAPNIC | 669 99% |
| 2401:f200::/32 | Valid | RIR databaseAPNIC, RADB | 634 100% |
| 103.52.13.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 149 22% |
| 203.81.80.0/22 | Valid | RIR databaseAPNIC, RADB | 149 22% |
| 136.228.172.0/22 | Valid | RIR databaseAPNIC, RADB | 63 9%low visibility |
| 203.81.93.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 63 9%low visibility |
| 203.81.95.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 63 9%low visibility |
| 203.81.76.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 5 1%low visibility |
| 203.81.76.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 5 1%low visibility |
AS-SET
AS9988's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 70 are in fix.csv.
- ROA: maxLength1
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced65
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 203.81.71.0/24 | ROA 203.81.64.0/19 AS9988 has maxLength 19; ROA 203.81.64.0/21 AS9988 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 203.81.71.0/24. |
| Route object: none | 203.81.71.0/24 | No route object for it. A route object for 203.81.68.0/22 with origin AS9988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9988 in the RIR database for the space. |
| ROA: none | 103.206.173.0/24 | No ROA covers it. Add a ROA for AS9988, maxLength 24. |
| Route object: RIR | 103.206.173.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.47.184.0/24 | No ROA covers it. Add a ROA for AS9988, maxLength 24. |
Route objects not announced
Route objects with origin AS9988 whose prefix no peer sees AS9988 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.224.40.0/24 | APNIC, RADB | Valid |
| 43.224.43.0/24 | APNIC, RADB | Valid |
| 45.41.100.0/23 | APNIC | Valid |
| 45.41.100.0/24 | APNIC | Valid |
| 45.41.101.0/24 | APNIC | Valid |
| 45.41.102.0/23 | APNIC | Valid |
| 45.41.102.0/24 | APNIC | Valid |
| 45.41.103.0/24 | APNIC | Valid |
| 45.41.104.0/22 | APNIC, RADB | Valid |
| 45.41.104.0/23 | APNIC | Valid |
| 45.41.106.0/23 | APNIC | Valid |
| 45.41.107.0/24 | APNIC | Valid |
| 45.41.108.0/23 | APNIC | Valid |
| 45.41.108.0/24 | APNIC, RADB | Valid |
| 45.41.109.0/24 | APNIC | Valid |
| 45.41.110.0/23 | APNIC | Valid |
| 45.41.110.0/24 | APNIC, RADB | Valid |
| 45.41.112.0/21 | APNIC | Valid |
| 45.41.112.0/22 | APNIC | Valid |
| 45.41.112.0/23 | APNIC | Valid |
| 45.41.112.0/24 | APNIC | Valid |
| 45.41.113.0/24 | APNIC | Valid |
| 45.41.114.0/23 | APNIC | Valid |
| 45.41.114.0/24 | APNIC | Valid |
| 45.41.115.0/24 | APNIC | Valid |
| 45.41.116.0/22 | APNIC | Valid |
| 45.41.116.0/23 | APNIC | Valid |
| 45.41.116.0/24 | APNIC | Valid |
| 45.41.117.0/24 | APNIC | Valid |
| 45.41.118.0/23 | APNIC | Valid |
| 45.41.118.0/24 | APNIC | Valid |
| 45.41.119.0/24 | APNIC | Valid |
| 45.41.120.0/21 | APNIC | Valid |
| 45.41.120.0/22 | APNIC | Valid |
| 45.41.120.0/23 | APNIC | Valid |
| 45.41.120.0/24 | APNIC | Valid |
| 45.41.121.0/24 | APNIC | Valid |
| 45.41.122.0/23 | APNIC | Valid |
| 45.41.122.0/24 | APNIC | Valid |
| 45.41.123.0/24 | APNIC | Valid |
| 45.41.124.0/22 | APNIC | Valid |
| 45.41.124.0/23 | APNIC | Valid |
| 45.41.124.0/24 | APNIC | Valid |
| 45.41.125.0/24 | APNIC | Valid |
| 45.41.126.0/23 | APNIC | Valid |
| 45.41.126.0/24 | APNIC | Valid |
| 45.41.127.0/24 | APNIC | Valid |
| 45.112.176.0/23 | APNIC, RADB | Valid |
| 45.112.178.0/23 | APNIC, RADB | Valid |
| 103.52.12.0/22 | APNIC, RADB | Valid |
| 103.52.12.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.52.14.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.52.15.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.77.201.0/24 | RADB | No ROA |
| 136.228.160.0/21 | APNIC | Valid |
| 136.228.160.0/23 | APNIC | Valid |
| 136.228.162.0/23 | APNIC | Valid |
| 136.228.164.0/23 | APNIC | Valid |
| 136.228.166.0/23 | APNIC | Valid |
| 136.228.168.0/21 | APNIC | Valid |
| 136.228.168.0/23 | APNIC | Valid |
| 136.228.170.0/23 | APNIC | Valid |
| 203.81.84.0/22 | APNIC, RADB | Valid |
| 203.81.92.0/24 | APNIC, NTTCOM, RADB | Valid |
| 2400:5f40::/32 | APNIC | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.