bgpreport

Network · data from 2026-11-12

AS132056 SCICUBE-AS - RM B, 2/F 88 KWAI CHEONG ROAD

Registry name: SCICUBE-AS - RM B, 2/F 88 KWAI CHEONG ROAD, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132056, 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.
43.241.72.0/23 No ROA Other IRR onlyRADB 670 100% 67
43.241.74.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
43.241.74.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
43.241.75.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
43.241.72.0/24 No ROA RIR databaseAPNIC, RADB 172 26% 55
43.241.73.0/24 No ROA RIR databaseAPNIC, RADB 172 26% 55
103.11.100.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
103.11.102.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
103.11.102.0/24 Valid RIR databaseAPNIC, RADB 172 26% 55
103.11.103.0/24 Valid RIR databaseAPNIC, RADB 168 25% 54
103.11.101.0/24 Valid RIR databaseAPNIC, RADB 156 23% 55
103.11.100.0/24 Valid RIR databaseAPNIC, RADB 82 12% 42

AS-SET

AS132056 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 16 are in fix.csv.

  • ROA: none6
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none43.241.72.0/23No ROA covers it. Add a ROA for AS132056, maxLength 23.670 of 673
Route object: RIR43.241.72.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none43.241.74.0/23No ROA covers it. Add a ROA for AS132056, maxLength 23.2 of 673
Route object: RIR43.241.74.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none43.241.74.0/24No ROA covers it. Add a ROA for AS132056, maxLength 24.671 of 673
ROA: none43.241.75.0/24No ROA covers it. Add a ROA for AS132056, maxLength 24.671 of 673
ROA: none43.241.72.0/24No ROA covers it. Add a ROA for AS132056, maxLength 24.172 of 673
ROA: none43.241.73.0/24No ROA covers it. Add a ROA for AS132056, maxLength 24.172 of 673

Route objects not announced

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

43.225.44.0/22NTTCOMNo ROA
43.230.188.0/22NTTCOMNo ROA
43.241.72.0/22NTTCOM, RADBNo ROA
43.242.128.0/22NTTCOMNo ROA
43.251.32.0/22NTTCOMNo ROA
43.252.168.0/22NTTCOMNo ROA
45.114.100.0/22NTTCOMNo ROA
103.11.100.0/22APNIC, NTTCOM, RADBValid

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.