Network · data from 2026-11-12

AS134976 MATL

Registry name: MATL-AS-AP - Myint & Associates Telecommunications Ltd, MM · PeeringDB

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

0IPv6 routes

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

0Route objects not announced registered with origin AS134976, seen from no peer

Announced routes

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


103.204.100.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
202.53.156.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
202.53.156.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
202.53.157.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
202.53.158.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
202.53.159.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.204.100.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	68
103.204.101.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	68
103.204.102.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	68
103.204.103.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	68

AS-SET

AS134976's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS134976 is announced.

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.