bgpreport

Network · data from 2026-11-12

AS24351 CNGI-BJ-IX5-AS-AP - CERNET2 IX at Beijing University of Aeronautics and Astronautics

Registry name: CNGI-BJ-IX5-AS-AP - CERNET2 IX at Beijing University of Aeronautics and Astronautics, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24351, 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:250:206::/48 Valid None 60 9%low visibility 36
2001:250:20a::/48 Valid None 60 9%low visibility 36
2001:250:20f::/48 Valid None 60 9%low visibility 36
2001:250:214::/48 Valid None 60 9%low visibility 36
2001:da8:ae::/48 Valid None 60 9%low visibility 36
2001:da8:bc::/48 Valid None 60 9%low visibility 36
2001:da8:203::/48 Valid None 60 9%low visibility 36
2001:da8:20a::/48 Valid None 60 9%low visibility 36
2001:da8:25f::/48 Valid None 60 9%low visibility 36
2001:da8:ffc::/48 Valid None 60 9%low visibility 36

AS-SET

AS24351 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 10 are in fix.csv.

  • Route object: none10
ChangePrefix or setDetailFull-table peers
Route object: none2001:250:206::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:250:20a::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:250:20f::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:250:214::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:da8:ae::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:da8:bc::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:da8:203::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:da8:20a::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:da8:25f::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636
Route object: none2001:da8:ffc::/48No route object for it. Add a route object with origin AS24351 in the RIR database for the space.60 of 636

Route objects not announced

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