bgpreport

Network · data from 2026-11-12

AS46003 KOREACENTER-AS-KR-KR - CONNECTWAVE

Registry name: KOREACENTER-AS-KR-KR - CONNECTWAVE, 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS46003, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS46003, 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.
14.129.64.0/24 No ROA Nonecovered by 14.129.0.0/16 672 100% 67
14.129.65.0/24 No ROA Nonecovered by 14.129.0.0/16 672 100% 67
14.129.66.0/24 No ROA Nonecovered by 14.129.0.0/16 672 100% 67
121.78.48.0/24 No ROA Other IRR onlyRADB 673 100% 67
182.161.122.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.238.177.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.238.182.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.238.183.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.246.167.0/24 No ROA Other IRR onlyRADB 673 100% 67
14.129.0.0/16 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS46003 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: none10
  • Route object: none3
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none14.129.64.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.672 of 673
Route object: none14.129.64.0/24No route object for it. A route object for 14.129.0.0/16 with origin AS46003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46003 in the RIR database for the space.672 of 673
ROA: none14.129.65.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.672 of 673
Route object: none14.129.65.0/24No route object for it. A route object for 14.129.0.0/16 with origin AS46003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46003 in the RIR database for the space.672 of 673
ROA: none14.129.66.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.672 of 673
Route object: none14.129.66.0/24No route object for it. A route object for 14.129.0.0/16 with origin AS46003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46003 in the RIR database for the space.672 of 673
ROA: none121.78.48.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.673 of 673
Route object: RIR121.78.48.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none182.161.122.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.673 of 673
Route object: RIR182.161.122.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.238.177.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.673 of 673
Route object: RIR203.238.177.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.238.182.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.673 of 673
Route object: RIR203.238.182.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.238.183.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.673 of 673
Route object: RIR203.238.183.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.246.167.0/24No ROA covers it. Add a ROA for AS46003, maxLength 24.673 of 673
Route object: RIR203.246.167.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none14.129.0.0/16No ROA covers it. Add a ROA for AS46003, maxLength 16.672 of 673
Route object: RIR14.129.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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