bgpreport

Network · data from 2026-11-12

AS55589 KITECH-AS-KR-KR - Korea Institute of Industrial Technology

Registry name: KITECH-AS-KR-KR - Korea Institute of Industrial Technology, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55589, 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.
203.247.217.16/30 Invalid: origin None 2 0%low visibility 2
203.250.109.240/28 No ROA Nonecovered by 203.250.109.0/24 16 2%low visibility 15
203.250.109.244/32 No ROA Nonecovered by 203.250.109.0/24 3 0%low visibility 3
203.250.104.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
203.250.105.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
203.250.106.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
203.250.107.0/24 No ROA Other IRR onlyRADB 672 100% 68
203.250.108.0/24 No ROA Other IRR onlyRADB 672 100% 68
203.250.109.0/24 No ROA Other IRR onlyRADB 672 100% 68
203.250.111.0/24 No ROA Other IRR onlyRADB 672 100% 68

AS-SET

AS55589 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 30 are in fix.csv.

  • ROA: origin1
  • ROA: none9
  • Route object: none3
  • Route object: RIR7
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin203.247.217.16/30ROAs covering it name AS1237, not AS55589. If AS55589 should announce it, add a ROA for AS55589.2 of 673
Route object: none203.247.217.16/30No route object for it. Add a route object with origin AS55589 in the RIR database for the space.2 of 673
ROA: none203.250.109.240/28No ROA covers it. Add a ROA for AS55589, maxLength 28.16 of 673
Route object: none203.250.109.240/28No route object for it. A route object for 203.250.109.0/24 with origin AS55589 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55589 in the RIR database for the space.16 of 673
ROA: none203.250.109.244/32No ROA covers it. Add a ROA for AS55589, maxLength 32.3 of 673
Route object: none203.250.109.244/32No route object for it. A route object for 203.250.109.0/24 with origin AS55589 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55589 in the RIR database for the space.3 of 673
ROA: none203.250.104.0/24No ROA covers it. Add a ROA for AS55589, maxLength 24.672 of 673
Route object: RIR203.250.104.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.250.105.0/24No ROA covers it. Add a ROA for AS55589, maxLength 24.672 of 673
Route object: RIR203.250.105.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.250.106.0/24No ROA covers it. Add a ROA for AS55589, maxLength 24.672 of 673
Route object: RIR203.250.106.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.250.107.0/24No ROA covers it. Add a ROA for AS55589, maxLength 24.672 of 673
Route object: RIR203.250.107.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.250.108.0/24No ROA covers it. Add a ROA for AS55589, maxLength 24.672 of 673
Route object: RIR203.250.108.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.250.109.0/24No ROA covers it. Add a ROA for AS55589, maxLength 24.672 of 673
Route object: RIR203.250.109.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.250.111.0/24No ROA covers it. Add a ROA for AS55589, maxLength 24.672 of 673
Route object: RIR203.250.111.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

59.0.49.0/24RADBNo ROA
121.148.122.0/23RADBNo ROA
121.148.124.0/22RADBNo ROA
121.170.25.0/24RADBNo ROA
121.170.26.0/23RADBNo ROA
121.170.28.0/22RADBNo ROA
121.174.120.0/22RADBNo ROA
121.174.124.0/24RADBNo ROA
203.241.116.0/22RADBNo ROA
203.250.104.0/21RADBNo 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.