bgpreport

Network · data from 2026-11-12

AS150788 Alternative Enterprises (HK)

Registry name: TROUBLE-AS - Alternative Enterprises, HK · PeeringDB

4IPv4 routes 75.0% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS150788, seen from no peer

Announced routes

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

44.31.161.0/24 No ROA Other IRR onlyRADB 673 100% 66
103.203.240.0/24 Valid RIR databaseAPNIC 673 100% 66
103.206.98.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
203.0.139.0/24 Valid RIR databaseAPNIC 672 100% 67
2400:e760:200::/48 Valid RIR databaseAPNIC, RADB 636 100% 68
2400:e760:300::/48 Valid RIR databaseAPNIC 636 100% 67
2400:e760:400::/48 Valid RIR databaseAPNIC 635 100% 69
2001:df2:10c0::/48 Valid RIR databaseAPNIC 634 100% 67
2400:e760:100::/48 Valid RIR databaseAPNIC 634 100% 67

AS-SET

AS150788'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 2 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none44.31.161.0/24No ROA covers it. Add a ROA for AS150788, maxLength 24.673 of 673
Route object: RIR44.31.161.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS150788 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.