bgpreport

Network · data from 2026-11-12

AS24409 CNNIC-CRITICAL-AP - China Internet Network Infomation Center

Registry name: CNNIC-CRITICAL-AP - China Internet Network Infomation Center, CN · not in PeeringDB

17IPv4 routes 0.0% RPKI valid · 100.0% with a route object
12IPv6 routes 8.3% RPKI valid · 83.3% with a route object
1RPKI invalid 1 origin · 0 maxLength
27No ROA 2 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
48Route objects not announced registered with origin AS24409, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24409, 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.

2a04:3e00::/29 Invalid: origin Other origin only 51 8%low visibility 31
2001:dc7:1::/48 No ROA Other IRR onlyRADB 449 71% 67
2001:dc7:fffc::/48 No ROA Other IRR onlyRADB 446 70% 64
125.208.45.0/24 No ROA Other IRR onlyRADB 171 25% 51
125.208.47.0/24 No ROA Other IRR onlyNTTCOM, RADB 171 25% 51
125.208.46.0/24 No ROA Other IRR onlyNTTCOM, RADB 144 21% 48
2001:dc7:fffd::/48 No ROA Other IRR onlyRADB 138 22% 45
2001:dc7:2::/48 No ROA Other IRR onlyRADB 135 21% 45
2001:dc7:fffb::/48 No ROA Other IRR onlyRADB 66 10% 36
2001:dc7:3::/48 No ROA Other IRR onlyRADB 39 6%low visibility 27
125.208.41.0/24 No ROA Other IRR onlyRADB 34 5%low visibility 21
125.208.42.0/24 No ROA Other IRR onlyRADB 21 3%low visibility 17
42.83.200.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
42.83.201.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
2001:dc7::/48 No ROA RIR databaseAPNIC, RADB 455 72% 60
203.119.29.0/24 No ROA RIR databaseAPNIC, RADB 453 67% 68
2001:dc7:fffe::/48 No ROA RIR databaseAPNIC, NTTCOM, RADB 448 70% 61
2001:dc7:1000::/48 No ROA RIR databaseAPNIC, NTTCOM, RADB 424 67% 59
2001:dc7:ffff::/48 No ROA RIR databaseAPNIC, RADB 373 59% 58
125.208.36.0/24 No ROA RIR databaseAPNIC, RADB 267 40% 52
203.119.27.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 240 36% 51
125.208.34.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 188 28% 54
203.119.28.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 159 24% 49
1.2.4.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 94 14% 35
125.208.33.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 65 10%low visibility 34
125.208.35.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 49 7%low visibility 32
203.119.26.0/24 No ROA RIR databaseAPNIC, NTTCOM 33 5%low visibility 28
125.208.43.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 3 0%low visibility 6
2a04:3e00:1002::/48 Valid None 635 100% 69

AS-SET

AS24409 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 89 are in fix.csv.

  • ROA: origin1
  • ROA: none27
  • Route object: none2
  • Route object: RIR11
  • Route object: not announced48
ChangePrefix or setDetailFull-table peers
ROA: origin2a04:3e00::/29ROAs covering it name AS48152, AS56910, not AS24409. If AS24409 should announce it, add a ROA for AS24409.51 of 636
Route object: none2a04:3e00::/29Route objects for it name AS48152, AS56910. Add a route object with origin AS24409 in the RIR database for the space.51 of 636
ROA: none2001:dc7:1::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.449 of 636
Route object: RIR2001:dc7:1::/48Route object only in RADB. Add it in the RIR database for the space.449 of 636
ROA: none2001:dc7:fffc::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.446 of 636
Route object: RIR2001:dc7:fffc::/48Route object only in RADB. Add it in the RIR database for the space.446 of 636
ROA: none125.208.45.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.171 of 673
Route object: RIR125.208.45.0/24Route object only in RADB. Add it in the RIR database for the space.171 of 673
ROA: none125.208.47.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.171 of 673
Route object: RIR125.208.47.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.171 of 673
ROA: none125.208.46.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.144 of 673
Route object: RIR125.208.46.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.144 of 673
ROA: none2001:dc7:fffd::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.138 of 636
Route object: RIR2001:dc7:fffd::/48Route object only in RADB. Add it in the RIR database for the space.138 of 636
ROA: none2001:dc7:2::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.135 of 636
Route object: RIR2001:dc7:2::/48Route object only in RADB. Add it in the RIR database for the space.135 of 636
ROA: none2001:dc7:fffb::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.66 of 636
Route object: RIR2001:dc7:fffb::/48Route object only in RADB. Add it in the RIR database for the space.66 of 636
ROA: none2001:dc7:3::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.39 of 636
Route object: RIR2001:dc7:3::/48Route object only in RADB. Add it in the RIR database for the space.39 of 636
ROA: none125.208.41.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.34 of 673
Route object: RIR125.208.41.0/24Route object only in RADB. Add it in the RIR database for the space.34 of 673
ROA: none125.208.42.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.21 of 673
Route object: RIR125.208.42.0/24Route object only in RADB. Add it in the RIR database for the space.21 of 673
ROA: none42.83.200.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.673 of 673
ROA: none42.83.201.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.673 of 673
ROA: none2001:dc7::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.455 of 636
ROA: none203.119.29.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.453 of 673
ROA: none2001:dc7:fffe::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.448 of 636
ROA: none2001:dc7:1000::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.424 of 636
ROA: none2001:dc7:ffff::/48No ROA covers it. Add a ROA for AS24409, maxLength 48.373 of 636
ROA: none125.208.36.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.267 of 673
ROA: none203.119.27.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.240 of 673
ROA: none125.208.34.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.188 of 673
ROA: none203.119.28.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.159 of 673
ROA: none1.2.4.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.94 of 673
ROA: none125.208.33.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.65 of 673
ROA: none125.208.35.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.49 of 673
ROA: none203.119.26.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.33 of 673
ROA: none125.208.43.0/24No ROA covers it. Add a ROA for AS24409, maxLength 24.3 of 673
Route object: none2a04:3e00:1002::/48No route object for it. Add a route object with origin AS24409 in the RIR database for the space.635 of 636

Route objects not announced

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

42.83.128.0/20APNIC, RADBNo ROA
42.83.130.0/24RADBNo ROA
42.83.131.0/24RADBNo ROA
42.83.132.0/24APNIC, RADBNo ROA
42.83.133.0/24APNIC, RADBNo ROA
42.83.134.0/24RADBNo ROA
42.83.199.0/24NTTCOM, RADBNo ROA
125.208.32.0/19APNIC, RADBNo ROA
125.208.32.0/24APNIC, RADBNo ROA
125.208.37.0/24RADBNo ROA
125.208.38.0/24RADBNo ROA
125.208.39.0/24RADBNo ROA
125.208.40.0/24RADBNo ROA
125.208.44.0/24APNIC, RADBNo ROA
125.208.49.0/24APNICNo ROA
203.119.24.0/21APNIC, RADBNo ROA
203.119.24.0/24APNICNo ROA
203.119.25.0/24APNIC, RADBNo ROA
203.119.30.0/24APNIC, RADBNo ROA
203.119.31.0/24APNIC, RADBNo ROA
203.119.32.0/22APNIC, RADBNo ROA
203.119.32.0/24APNICNo ROA
203.119.33.0/24APNICNo ROA
203.119.34.0/24APNICNo ROA
203.119.35.0/24APNICNo ROA
210.2.4.0/24APNIC, NTTCOM, RADBNo ROA
2001:dc7::/32APNIC, RADBNo ROA
2001:dc7:a::/48APNIC, RADBNo ROA
2001:dc7:b::/48APNIC, RADBNo ROA
2001:dc7:dd01::/48APNICNo ROA
2001:dc7:dd04::/48APNICNo ROA
2001:dc7:ddff::/48APNICNo ROA
2001:dc7:feff::/48APNICNo ROA
2001:dc7:ffc0::/48APNICNo ROA
2001:dc7:ffc1::/48APNIC, RADBNo ROA
2001:dc7:ffc2::/48APNIC, RADBNo ROA
2001:dc7:ffc3::/48APNIC, RADBNo ROA
2001:dc7:ffc4::/48APNIC, RADBNo ROA
2001:dc7:ffc5::/48APNIC, RADBNo ROA
2001:dc7:ffc6::/48APNIC, RADBNo ROA
2001:dc7:ffd1::/48APNIC, RADBNo ROA
2001:dc7:ffd2::/48APNIC, RADBNo ROA
2001:dc7:ffd3::/48APNIC, RADBNo ROA
2001:dc7:ffd6::/48APNICNo ROA
2001:dc7:ffeb::/48APNIC, RADBNo ROA
2001:dc7:ffec::/48APNIC, RADBNo ROA
2002:dc7::/48NTTCOMNo ROA
2406:2700::/32APNICNo 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.