bgpreport

Network · data from 2026-11-12

AS24302 CRIS-CERNET-AS - CRIS-CERNET

Registry name: CRIS-CERNET-AS - CRIS-CERNET, CN · not in PeeringDB

0IPv4 routes
1IPv6 routes 0.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
21Route objects not announced registered with origin AS24302, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24302, 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.
2001:dd9::/48 No ROA RIR databaseAPNIC 634 100% 70

AS-SET

AS24302 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 22 are in fix.csv.

  • ROA: none1
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none2001:dd9::/48No ROA covers it. Add a ROA for AS24302, maxLength 48.634 of 636

Route objects not announced

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

103.3.0.0/19RADBNo ROA
103.3.0.0/20RADBNo ROA
103.3.0.0/21RADBNo ROA
103.3.8.0/21RADBNo ROA
103.3.12.0/22RADBNo ROA
103.3.12.0/23RADBNo ROA
103.3.12.0/24RADBNo ROA
103.3.13.0/24RADBNo ROA
103.3.14.0/23RADBNo ROA
103.3.14.0/24RADBNo ROA
103.3.15.0/24RADBNo ROA
103.3.16.0/20RADBNo ROA
103.3.16.0/21RADBNo ROA
103.3.24.0/21RADBNo ROA
103.3.28.0/22RADBNo ROA
103.3.28.0/23RADBNo ROA
103.3.30.0/23RADBNo ROA
103.137.60.0/24APNICNo ROA
103.137.60.0/25APNICNo ROA
103.137.60.128/25APNICNo ROA
202.38.109.0/24APNICNo 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.