bgpreport

Network · data from 2026-11-12

AS46009 YABESK-AS-KR-KR - YABESK

Registry name: YABESK-AS-KR-KR - YABESK, KR · not in PeeringDB

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

Announced routes

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

58.103.8.0/23 No ROA Nonecovered by 58.103.8.0/22 673 100% 67
121.137.87.0/24 No ROA None 673 100% 67
121.137.88.0/24 No ROA None 673 100% 67
121.137.89.0/24 No ROA None 673 100% 67
121.137.90.0/24 No ROA None 673 100% 67
121.137.94.0/24 No ROA None 673 100% 67
121.137.95.0/24 No ROA None 673 100% 67
121.137.96.0/24 No ROA None 673 100% 67
121.137.105.0/24 No ROA None 673 100% 67
121.137.106.0/24 No ROA None 673 100% 67
121.137.107.0/24 No ROA None 673 100% 67
211.221.104.0/26 No ROA Nonecovered by 211.221.104.0/24 14 2%low visibility 13
211.221.104.192/26 No ROA Nonecovered by 211.221.104.0/24 14 2%low visibility 13
211.221.104.176/28 No ROA Nonecovered by 211.221.104.0/24 13 2%low visibility 13
58.103.2.0/23 No ROA Other IRR onlyRADB 673 100% 66
58.103.2.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
58.103.3.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
58.103.4.0/22 No ROA Other IRR onlyRADB 673 100% 67
58.103.4.0/23 No ROA Other IRR onlyNTTCOM 673 100% 67
58.103.4.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
58.103.5.0/24 No ROA Other IRR onlyRADB 673 100% 66
58.103.6.0/24 No ROA Other IRR onlyNTTCOM 673 100% 66
58.103.7.0/24 No ROA Other IRR onlyNTTCOM 673 100% 66
58.103.8.0/22 No ROA Other IRR onlyRADB 673 100% 67
58.103.8.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
58.103.9.0/24 No ROA Other IRR onlyRADB 673 100% 66
58.103.10.0/24 No ROA Other IRR onlyNTTCOM 673 100% 66
58.103.11.0/24 No ROA Other IRR onlyNTTCOM 673 100% 66
59.14.102.0/23 No ROA Other IRR onlyNTTCOM 673 100% 67
59.14.104.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
59.14.123.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
59.14.124.0/23 No ROA Other IRR onlyNTTCOM 673 100% 67
59.14.124.0/24 No ROA Other IRR onlyRADB 673 100% 67
59.14.125.0/24 No ROA Other IRR onlyRADB 673 100% 67
59.14.126.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
175.196.208.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
211.221.104.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
218.148.22.0/23 No ROA Other IRR onlyNTTCOM 673 100% 67
14.35.192.0/22 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
14.35.196.0/22 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66

AS-SET

AS46009 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 80 are in fix.csv.

  • ROA: none40
  • Route object: none14
  • Route object: RIR26
ChangePrefix or setDetailFull-table peers
ROA: none58.103.8.0/23No ROA covers it. Add a ROA for AS46009, maxLength 23.673 of 673
Route object: none58.103.8.0/23No route object for it. A route object for 58.103.8.0/22 with origin AS46009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.87.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.87.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.88.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.88.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.89.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.89.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.90.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.90.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.94.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.94.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.95.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.95.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.96.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.96.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.105.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.105.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.106.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.106.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none121.137.107.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: none121.137.107.0/24No route object for it. Add a route object with origin AS46009 in the RIR database for the space.673 of 673
ROA: none211.221.104.0/26No ROA covers it. Add a ROA for AS46009, maxLength 26.14 of 673
Route object: none211.221.104.0/26No route object for it. A route object for 211.221.104.0/24 with origin AS46009 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46009 in the RIR database for the space.14 of 673
ROA: none211.221.104.192/26No ROA covers it. Add a ROA for AS46009, maxLength 26.14 of 673
Route object: none211.221.104.192/26No route object for it. A route object for 211.221.104.0/24 with origin AS46009 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46009 in the RIR database for the space.14 of 673
ROA: none211.221.104.176/28No ROA covers it. Add a ROA for AS46009, maxLength 28.13 of 673
Route object: none211.221.104.176/28No route object for it. A route object for 211.221.104.0/24 with origin AS46009 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46009 in the RIR database for the space.13 of 673
ROA: none58.103.2.0/23No ROA covers it. Add a ROA for AS46009, maxLength 23.673 of 673
Route object: RIR58.103.2.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none58.103.2.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.2.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.103.3.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.3.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.103.4.0/22No ROA covers it. Add a ROA for AS46009, maxLength 22.673 of 673
Route object: RIR58.103.4.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none58.103.4.0/23No ROA covers it. Add a ROA for AS46009, maxLength 23.673 of 673
Route object: RIR58.103.4.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.103.4.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.4.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.103.5.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.5.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none58.103.6.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.6.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.103.7.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.7.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.103.8.0/22No ROA covers it. Add a ROA for AS46009, maxLength 22.673 of 673
Route object: RIR58.103.8.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none58.103.8.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.8.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.103.9.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.9.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none58.103.10.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.10.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.103.11.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR58.103.11.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none59.14.102.0/23No ROA covers it. Add a ROA for AS46009, maxLength 23.673 of 673
Route object: RIR59.14.102.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none59.14.104.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR59.14.104.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none59.14.123.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR59.14.123.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none59.14.124.0/23No ROA covers it. Add a ROA for AS46009, maxLength 23.673 of 673
Route object: RIR59.14.124.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none59.14.124.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR59.14.124.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none59.14.125.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR59.14.125.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none59.14.126.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR59.14.126.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none175.196.208.0/22No ROA covers it. Add a ROA for AS46009, maxLength 22.673 of 673
Route object: RIR175.196.208.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.221.104.0/24No ROA covers it. Add a ROA for AS46009, maxLength 24.673 of 673
Route object: RIR211.221.104.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none218.148.22.0/23No ROA covers it. Add a ROA for AS46009, maxLength 23.673 of 673
Route object: RIR218.148.22.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none14.35.192.0/22No ROA covers it. Add a ROA for AS46009, maxLength 22.672 of 673
Route object: RIR14.35.192.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none14.35.196.0/22No ROA covers it. Add a ROA for AS46009, maxLength 22.672 of 673
Route object: RIR14.35.196.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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