bgpreport

Network · data from 2026-11-12

AS151487 AWESOMECLOUD-AS-AP - Awesomecloud Limited

Registry name: AWESOMECLOUD-AS-AP - Awesomecloud Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS151487, 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.93.3.0/24 Invalid: origin Other origin only 1 0%low visibility 1
107.148.100.0/24 Valid Other IRR onlyRADB 670 100% 67
107.148.101.0/24 Valid Other IRR onlyRADB 670 100% 67
104.234.155.0/24 Valid RIR databaseARIN, RADB 670 100% 67
103.160.100.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67

AS-SET

AS151487 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 11 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin154.93.3.0/24ROAs covering it name AS17561, AS214143, not AS151487. If AS151487 should announce it, add a ROA for AS151487.1 of 673
Route object: none154.93.3.0/24Route objects for it name AS214143. Add a route object with origin AS151487 in the RIR database for the space.1 of 673
Route object: RIR107.148.100.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR107.148.101.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

38.69.240.0/24RADBNo ROA
38.69.241.0/24RADBNo ROA
38.69.242.0/24RADBNo ROA
38.209.64.0/21RADBNo ROA
107.148.100.0/23ARIN, RADBValid
123.108.70.0/24APNIC, RADBValid
154.36.144.0/21RADBNo 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.