bgpreport

Network · data from 2026-11-12

AS149487 MCLOCCL-AS-AP - MOC COMPANY LIMITED

Registry name: MCLOCCL-AS-AP - MOC COMPANY LIMITED, MM · not in PeeringDB

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

Announced routes

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

154.21.22.0/24 Valid Nonecovered by 154.21.22.0/23 672 100% 67
103.181.26.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.181.26.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.181.27.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
154.21.22.0/23 Valid RIR databaseARIN 673 100% 67

AS-SET

AS149487 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 32 are in fix.csv.

  • Route object: none1
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
Route object: none154.21.22.0/24No route object for it. A route object for 154.21.22.0/23 with origin AS149487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149487 in the RIR database for the space.672 of 673

Route objects not announced

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

2400:57a0::/32APNICValid
2400:57a0::/33APNICValid
2400:57a0::/34APNICValid
2400:57a0::/35APNICValid
2400:57a0::/36APNICValid
2400:57a0:1000::/36APNICValid
2400:57a0:2000::/35APNICValid
2400:57a0:2000::/36APNICValid
2400:57a0:3000::/36APNICValid
2400:57a0:4000::/34APNICValid
2400:57a0:4000::/35APNICValid
2400:57a0:4000::/36APNICValid
2400:57a0:5000::/36APNICValid
2400:57a0:6000::/35APNICValid
2400:57a0:6000::/36APNICValid
2400:57a0:7000::/36APNICValid
2400:57a0:8000::/33APNICValid
2400:57a0:8000::/34APNICValid
2400:57a0:8000::/35APNICValid
2400:57a0:8000::/36APNICValid
2400:57a0:9000::/36APNICValid
2400:57a0:a000::/35APNICValid
2400:57a0:a000::/36APNICValid
2400:57a0:b000::/36APNICValid
2400:57a0:c000::/34APNICValid
2400:57a0:c000::/35APNICValid
2400:57a0:c000::/36APNICValid
2400:57a0:d000::/36APNICValid
2400:57a0:e000::/35APNICValid
2400:57a0:e000::/36APNICValid
2400:57a0:f000::/36APNICValid

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.