bgpreport

Network · data from 2026-11-12

AS141015 Myanmar Link Telecommunication

Registry name: MYANMARLINK-AS-AP - Myanmar Link Telecommunication Ltd, MM · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 50.0% RPKI valid · 50.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS141015, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS141015, 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.
2407:e340::/36 Invalid: maxLength Nonecovered by 2407:e340::/32 7 1%low visibility 5
103.154.240.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.154.241.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
2407:e340::/32 Valid RIR databaseAPNIC, RADB 636 100% 69

AS-SET

AS141015'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 3 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2407:e340::/36ROA 2407:e340::/32 AS141015 has maxLength 32; the route is a /36. Raise the maxLength, or add a ROA for 2407:e340::/36.7 of 636
Route object: none2407:e340::/36No route object for it. A route object for 2407:e340::/32 with origin AS141015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS141015 in the RIR database for the space.7 of 636

Route objects not announced

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

103.154.240.0/23APNIC, NTTCOM, RADBValid

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.