bgpreport

Network · data from 2026-11-12

AS133953 MTCL-AS-AP - Mega Target Communication Limited

Registry name: MTCL-AS-AP - Mega Target Communication Limited, HK · not in PeeringDB

7IPv4 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
9Route objects not announced registered with origin AS133953, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133953, 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.49.246.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.252.244.0/24 Valid RIR databaseAPNIC 673 100% 67
210.211.30.0/23 Valid RIR databaseAPNIC 672 100% 67
103.49.246.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.49.247.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
210.211.30.0/24 Valid RIR databaseAPNIC 670 100% 67
210.211.31.0/24 Valid RIR databaseAPNIC 670 100% 67

AS-SET

AS133953 isn't in PeeringDB, where networks name their 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 9 are in fix.csv.

  • Route object: not announced9

Route objects not announced

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

103.18.182.0/23APNIC, NTTCOM, RADBNo ROA
103.18.182.0/24APNIC, NTTCOM, RADBNo ROA
103.18.183.0/24APNIC, NTTCOM, RADBNo ROA
103.196.86.0/23NTTCOM, RADBNo ROA
103.196.86.0/24NTTCOM, RADBNo ROA
103.196.87.0/24NTTCOM, RADBNo ROA
103.208.0.0/23NTTCOM, RADBNo ROA
103.208.0.0/24NTTCOM, RADBNo ROA
103.208.1.0/24NTTCOM, RADBNo 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.