bgpreport

Network · data from 2026-11-12

AS17600 ENVICO-AS-KR-KR - KOREA RESOURCES RECOVERY AND REUTILIZATION CORPORATION

Registry name: ENVICO-AS-KR-KR - KOREA RESOURCES RECOVERY AND REUTILIZATION CORPORATION, KR · not in PeeringDB

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

Announced routes

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

125.133.155.0/24 No ROA None 673 100% 67
210.90.44.0/24 No ROA None 673 100% 67
210.99.81.0/24 No ROA None 673 100% 67
61.108.47.128/25 No ROA Nonecovered by 61.108.47.0/24 16 2%low visibility 13
210.104.107.128/26 No ROA Other origin only 14 2%low visibility 13
210.104.107.192/26 No ROA Other origin only 14 2%low visibility 13
61.108.48.0/24 No ROA Other IRR onlyRADB 673 100% 67
61.108.90.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.104.107.0/25 No ROA Other IRR onlyRADB 3 0%low visibility 3

AS-SET

AS17600 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: none9
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none125.133.155.0/24No ROA covers it. Add a ROA for AS17600, maxLength 24.673 of 673
Route object: none125.133.155.0/24No route object for it. Add a route object with origin AS17600 in the RIR database for the space.673 of 673
ROA: none210.90.44.0/24No ROA covers it. Add a ROA for AS17600, maxLength 24.673 of 673
Route object: none210.90.44.0/24No route object for it. Add a route object with origin AS17600 in the RIR database for the space.673 of 673
ROA: none210.99.81.0/24No ROA covers it. Add a ROA for AS17600, maxLength 24.673 of 673
Route object: none210.99.81.0/24No route object for it. Add a route object with origin AS17600 in the RIR database for the space.673 of 673
ROA: none61.108.47.128/25No ROA covers it. Add a ROA for AS17600, maxLength 25.16 of 673
Route object: none61.108.47.128/25No route object for it. A route object for 61.108.47.0/24 with origin AS17600 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS17600 in the RIR database for the space.16 of 673
ROA: none210.104.107.128/26No ROA covers it. Add a ROA for AS17600, maxLength 26.14 of 673
Route object: none210.104.107.128/26Route objects for it name AS9969. Add a route object with origin AS17600 in the RIR database for the space.14 of 673
ROA: none210.104.107.192/26No ROA covers it. Add a ROA for AS17600, maxLength 26.14 of 673
Route object: none210.104.107.192/26Route objects for it name AS9969. Add a route object with origin AS17600 in the RIR database for the space.14 of 673
ROA: none61.108.48.0/24No ROA covers it. Add a ROA for AS17600, maxLength 24.673 of 673
Route object: RIR61.108.48.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none61.108.90.0/24No ROA covers it. Add a ROA for AS17600, maxLength 24.673 of 673
Route object: RIR61.108.90.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.104.107.0/25No ROA covers it. Add a ROA for AS17600, maxLength 25.3 of 673
Route object: RIR210.104.107.0/25Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

61.108.47.0/24RADBNo ROA
210.206.200.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.