Network · data from 2026-11-12

AS136480 Myanmar Unilink

Registry name: MMUNILINK-AS-AP - Myanmar Unilink Communication Company Limited, MM · PeeringDB

20IPv4 routes 100.0% RPKI valid · 100.0% with a route object

17IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

12Route objects not announced registered with origin AS136480, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136480, 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.


43.227.12.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
43.227.12.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
43.227.13.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
43.227.15.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.89.176.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.89.176.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.89.177.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.89.178.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.89.179.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.116.56.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.116.56.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
103.116.57.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
103.134.204.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.134.205.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
103.134.206.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.134.207.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
103.116.59.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	671 100%	67
103.134.204.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	671 100%	67
43.227.14.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	67
103.116.58.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	67
2400:f1c0::/32	Valid	RIR databaseAPNIC	636 100%	67
2400:f1c0::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:1::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:2::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:3::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:4::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:5::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:6::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:7::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:8::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:9::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:a::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:b::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:c::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:d::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:e::/48	Valid	RIR databaseAPNIC	635 100%	69
2400:f1c0:f::/48	Valid	RIR databaseAPNIC	635 100%	69

AS-SET

AS136480'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 12 are in fix.csv.

Route object: not announced12

Route objects not announced

Route objects with origin AS136480 whose prefix no peer sees AS136480 announce. Many are kept on purpose (backup routes, space announced only in some places).


45.201.232.0/21	NTTCOM	No ROA
45.201.232.0/22	NTTCOM, RADB	No ROA
45.201.232.0/23	NTTCOM, RADB	No ROA
45.201.234.0/23	NTTCOM, RADB	No ROA
45.201.236.0/22	NTTCOM	No ROA
45.201.236.0/23	NTTCOM	No ROA
45.201.238.0/23	NTTCOM	No ROA
103.116.56.0/23	APNIC, NTTCOM, RADB	Valid
103.116.58.0/23	APNIC, NTTCOM, RADB	Valid
103.146.48.0/23	NTTCOM, RADB	No ROA
103.146.48.0/24	NTTCOM, RADB	No ROA
103.146.49.0/24	NTTCOM, RADB	No ROA

45.201.232.0/21

NTTCOM

No ROA

45.201.232.0/22

NTTCOM, RADB

No ROA

45.201.232.0/23

NTTCOM, RADB

No ROA

45.201.234.0/23

NTTCOM, RADB

No ROA

45.201.236.0/22

NTTCOM

No ROA

45.201.236.0/23

NTTCOM

No ROA

45.201.238.0/23

NTTCOM

No ROA

103.116.56.0/23

APNIC, NTTCOM, RADB

Valid

103.116.58.0/23

APNIC, NTTCOM, RADB

Valid

103.146.48.0/23

NTTCOM, RADB

No ROA

103.146.48.0/24

NTTCOM, RADB

No ROA

103.146.49.0/24

NTTCOM, RADB

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.