bgpreport

Network · data from 2026-11-12

AS53359 CUBE-NETWORK - CUBE Global Storage Ltd.

Registry name: CUBE-NETWORK - CUBE Global Storage Ltd., CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53359, 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.
64.141.5.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 67
64.251.76.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 67
72.2.4.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 67
72.2.6.0/24 No ROA Other IRR onlyALTDB 670 100% 67
198.162.87.0/24 No ROA Other IRR onlyALTDB 670 100% 67
204.239.206.0/24 No ROA Other IRR onlyALTDB 670 100% 67
144.208.80.0/22 No ROA Other IRR onlyALTDB, RADB 642 95% 67
23.152.132.0/24 Valid RIR databaseARIN 671 100% 67
206.197.223.0/24 Valid RIR databaseARIN 671 100% 67
2602:f446::/40 Valid RIR databaseARIN 634 100% 68

AS-SET

AS53359 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: none7
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none64.141.5.0/24No ROA covers it. Add a ROA for AS53359, maxLength 24.671 of 673
Route object: RIR64.141.5.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none64.251.76.0/24No ROA covers it. Add a ROA for AS53359, maxLength 24.671 of 673
Route object: RIR64.251.76.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none72.2.4.0/22No ROA covers it. Add a ROA for AS53359, maxLength 22.671 of 673
Route object: RIR72.2.4.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none72.2.6.0/24No ROA covers it. Add a ROA for AS53359, maxLength 24.670 of 673
Route object: RIR72.2.6.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none198.162.87.0/24No ROA covers it. Add a ROA for AS53359, maxLength 24.670 of 673
Route object: RIR198.162.87.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none204.239.206.0/24No ROA covers it. Add a ROA for AS53359, maxLength 24.670 of 673
Route object: RIR204.239.206.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none144.208.80.0/22No ROA covers it. Add a ROA for AS53359, maxLength 22.642 of 673
Route object: RIR144.208.80.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.642 of 673

Route objects not announced

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

64.251.78.0/23RADBNo ROA
204.239.181.0/24RADBNo 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.