bgpreport

Network · data from 2026-11-12

AS55468 CRI - China Radio International

Registry name: CRI - China Radio International, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55468, 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.248.112.0/22 No ROA None 673 100% 67
103.39.204.0/24 No ROA None 673 100% 67
103.39.205.0/24 No ROA None 673 100% 67
103.39.206.0/24 No ROA None 673 100% 67
103.39.207.0/24 No ROA None 673 100% 67
122.10.133.0/24 No ROA Other origin onlycovered by 122.10.132.0/22 673 100% 67
122.10.136.0/24 No ROA Other origin onlycovered by 122.10.136.0/21 673 100% 67
122.10.137.0/24 No ROA Other origin onlycovered by 122.10.136.0/21 673 100% 67

AS-SET

AS55468 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 20 are in fix.csv.

  • ROA: none8
  • Route object: none8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none43.248.112.0/22No ROA covers it. Add a ROA for AS55468, maxLength 22.673 of 673
Route object: none43.248.112.0/22No route object for it. Add a route object with origin AS55468 in the RIR database for the space.673 of 673
ROA: none103.39.204.0/24No ROA covers it. Add a ROA for AS55468, maxLength 24.673 of 673
Route object: none103.39.204.0/24No route object for it. Add a route object with origin AS55468 in the RIR database for the space.673 of 673
ROA: none103.39.205.0/24No ROA covers it. Add a ROA for AS55468, maxLength 24.673 of 673
Route object: none103.39.205.0/24No route object for it. Add a route object with origin AS55468 in the RIR database for the space.673 of 673
ROA: none103.39.206.0/24No ROA covers it. Add a ROA for AS55468, maxLength 24.673 of 673
Route object: none103.39.206.0/24No route object for it. Add a route object with origin AS55468 in the RIR database for the space.673 of 673
ROA: none103.39.207.0/24No ROA covers it. Add a ROA for AS55468, maxLength 24.673 of 673
Route object: none103.39.207.0/24No route object for it. Add a route object with origin AS55468 in the RIR database for the space.673 of 673
ROA: none122.10.133.0/24No ROA covers it. Add a ROA for AS55468, maxLength 24.673 of 673
Route object: none122.10.133.0/24Route objects for it name AS38197. A route object for 122.10.132.0/22 with origin AS55468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55468 in the RIR database for the space.673 of 673
ROA: none122.10.136.0/24No ROA covers it. Add a ROA for AS55468, maxLength 24.673 of 673
Route object: none122.10.136.0/24Route objects for it name AS38197. A route object for 122.10.136.0/21 with origin AS55468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55468 in the RIR database for the space.673 of 673
ROA: none122.10.137.0/24No ROA covers it. Add a ROA for AS55468, maxLength 24.673 of 673
Route object: none122.10.137.0/24Route objects for it name AS38197. A route object for 122.10.136.0/21 with origin AS55468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55468 in the RIR database for the space.673 of 673

Route objects not announced

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

122.10.132.0/22NTTCOM, RADBNo ROA
122.10.136.0/21NTTCOM, RADBNo ROA
122.10.144.0/20NTTCOMNo ROA
122.10.160.0/22NTTCOMNo 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.