bgpreport

Network · data from 2026-11-12

AS17859 CBNET-AS-KR-KR - NICEINFOMATIONSERVICE

Registry name: CBNET-AS-KR-KR - NICEINFOMATIONSERVICE, KR · not in PeeringDB

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

Announced routes

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

119.192.231.0/24 No ROA None 673 100% 67
121.131.196.192/27 No ROA None 14 2%low visibility 13
123.111.63.64/26 No ROA None 14 2%low visibility 13
121.162.154.0/24 No ROA Other IRR onlyRADB 673 100% 66
121.162.155.0/24 No ROA Other IRR onlyRADB 673 100% 66
211.218.41.0/24 No ROA Other IRR onlyRADB 673 100% 66
211.219.64.0/24 No ROA Other IRR onlyRADB 673 100% 66
218.153.128.0/24 No ROA Other IRR onlyRADB 673 100% 66
218.232.34.0/24 No ROA Other IRR onlyRADB 673 100% 66
220.75.210.0/24 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS17859 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 85 are in fix.csv.

  • ROA: none10
  • Route object: none3
  • Route object: RIR7
  • Route object: not announced65
ChangePrefix or setDetailFull-table peers
ROA: none119.192.231.0/24No ROA covers it. Add a ROA for AS17859, maxLength 24.673 of 673
Route object: none119.192.231.0/24No route object for it. Add a route object with origin AS17859 in the RIR database for the space.673 of 673
ROA: none121.131.196.192/27No ROA covers it. Add a ROA for AS17859, maxLength 27.14 of 673
Route object: none121.131.196.192/27No route object for it. Add a route object with origin AS17859 in the RIR database for the space.14 of 673
ROA: none123.111.63.64/26No ROA covers it. Add a ROA for AS17859, maxLength 26.14 of 673
Route object: none123.111.63.64/26No route object for it. Add a route object with origin AS17859 in the RIR database for the space.14 of 673
ROA: none121.162.154.0/24No ROA covers it. Add a ROA for AS17859, maxLength 24.673 of 673
Route object: RIR121.162.154.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none121.162.155.0/24No ROA covers it. Add a ROA for AS17859, maxLength 24.673 of 673
Route object: RIR121.162.155.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.218.41.0/24No ROA covers it. Add a ROA for AS17859, maxLength 24.673 of 673
Route object: RIR211.218.41.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.219.64.0/24No ROA covers it. Add a ROA for AS17859, maxLength 24.673 of 673
Route object: RIR211.219.64.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none218.153.128.0/24No ROA covers it. Add a ROA for AS17859, maxLength 24.673 of 673
Route object: RIR218.153.128.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none218.232.34.0/24No ROA covers it. Add a ROA for AS17859, maxLength 24.673 of 673
Route object: RIR218.232.34.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.75.210.0/24No ROA covers it. Add a ROA for AS17859, maxLength 24.673 of 673
Route object: RIR220.75.210.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

121.78.79.0/24RADBNo ROA
121.78.80.0/24RADBNo ROA
121.78.87.0/24RADBNo ROA
121.78.95.0/24RADBNo ROA
121.78.112.0/24RADBNo ROA
121.78.113.0/24RADBNo ROA
121.78.114.0/24RADBNo ROA
121.78.115.0/24RADBNo ROA
121.78.116.0/24RADBNo ROA
121.78.117.0/24RADBNo ROA
121.78.118.0/24RADBNo ROA
121.78.119.0/24RADBNo ROA
121.78.121.0/24RADBNo ROA
121.78.122.0/24RADBNo ROA
121.78.123.0/24RADBNo ROA
121.78.124.0/24RADBNo ROA
121.78.125.0/24RADBNo ROA
121.78.126.0/24RADBNo ROA
121.78.127.0/24RADBNo ROA
121.78.128.0/24RADBNo ROA
121.78.129.0/24RADBNo ROA
121.78.130.0/24RADBNo ROA
121.78.131.0/24RADBNo ROA
121.78.132.0/24RADBNo ROA
121.78.133.0/24RADBNo ROA
121.78.134.0/24RADBNo ROA
121.78.144.0/24RADBNo ROA
121.78.145.0/24RADBNo ROA
121.78.146.0/24RADBNo ROA
121.78.147.0/24RADBNo ROA
121.78.176.0/24RADBNo ROA
121.78.177.0/24RADBNo ROA
121.78.178.0/24RADBNo ROA
121.78.179.0/24RADBNo ROA
180.131.0.0/24RADBNo ROA
180.131.1.0/24RADBNo ROA
180.131.2.0/24RADBNo ROA
180.131.3.0/24RADBNo ROA
180.131.6.0/24RADBNo ROA
180.131.7.0/24RADBNo ROA
180.131.10.0/24RADBNo ROA
180.131.11.0/24RADBNo ROA
180.131.12.0/24RADBNo ROA
180.131.13.0/24RADBNo ROA
180.131.14.0/24RADBNo ROA
180.131.26.0/24RADBNo ROA
180.131.27.0/24RADBNo ROA
180.131.28.0/24RADBNo ROA
180.131.29.0/24RADBNo ROA
180.131.30.0/24RADBNo ROA
180.131.31.0/24RADBNo ROA
180.131.32.0/19RADBNo ROA
183.86.224.0/19RADBNo ROA
203.234.212.0/23RADBNo ROA
203.234.212.0/24RADBNo ROA
203.234.213.0/24RADBNo ROA
203.234.228.0/24RADBNo ROA
203.236.117.0/25RADBNo ROA
211.201.198.0/24RADBNo ROA
211.211.38.0/24RADBNo ROA
211.226.218.0/24RADBNo ROA
211.244.211.0/24RADBNo ROA
218.156.80.0/24RADBNo ROA
219.241.221.0/24RADBNo ROA
222.236.221.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.