bgpreport

Network · data from 2026-11-12

AS9645 HYUNDAIFUTURES-AS-KR - NEXT SECURITIES CORPORATION

Registry name: HYUNDAIFUTURES-AS-KR - NEXT SECURITIES CORPORATION, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9645, 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.240.128.224/27 No ROA Nonecovered by 203.240.128.0/24 14 2%low visibility 13
124.137.14.0/24 No ROA Other IRR onlyRADB 673 100% 66
203.240.128.0/24 No ROA Other IRR onlyRADB 673 100% 66
211.47.38.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS9645 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 10 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none203.240.128.224/27No ROA covers it. Add a ROA for AS9645, maxLength 27.14 of 673
Route object: none203.240.128.224/27No route object for it. A route object for 203.240.128.0/24 with origin AS9645 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS9645 in the RIR database for the space.14 of 673
ROA: none124.137.14.0/24No ROA covers it. Add a ROA for AS9645, maxLength 24.673 of 673
Route object: RIR124.137.14.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.240.128.0/24No ROA covers it. Add a ROA for AS9645, maxLength 24.673 of 673
Route object: RIR203.240.128.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.47.38.0/24No ROA covers it. Add a ROA for AS9645, maxLength 24.673 of 673
Route object: RIR211.47.38.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 AS9645 whose prefix no peer sees AS9645 announce. Many are kept on purpose (backup routes, space announced only in some places).

124.111.189.0/25RADBNo ROA
183.111.93.192/26RADBNo 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.