bgpreport

Network · data from 2026-11-12

AS17570 SKGLOBAL-AS-KR-KR - SK Global co., Ltd

Registry name: SKGLOBAL-AS-KR-KR - SK Global co., Ltd, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17570, 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.
206.219.0.0/20 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
206.219.16.0/21 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
206.219.24.0/24 No ROA Other IRR onlyRADB 672 100% 66
206.219.32.0/22 No ROA Other IRR onlyRADB 672 100% 66
206.219.36.0/22 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
206.219.43.0/24 No ROA Other IRR onlyRADB 672 100% 66
206.219.44.0/24 No ROA Other IRR onlyRADB 672 100% 66
206.219.45.0/24 No ROA Other IRR onlyRADB 672 100% 66
206.219.60.0/22 No ROA Other IRR onlyRADB 672 100% 66

AS-SET

AS17570 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 21 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none206.219.0.0/20No ROA covers it. Add a ROA for AS17570, maxLength 20.672 of 673
Route object: RIR206.219.0.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.219.16.0/21No ROA covers it. Add a ROA for AS17570, maxLength 21.672 of 673
Route object: RIR206.219.16.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.219.24.0/24No ROA covers it. Add a ROA for AS17570, maxLength 24.672 of 673
Route object: RIR206.219.24.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.219.32.0/22No ROA covers it. Add a ROA for AS17570, maxLength 22.672 of 673
Route object: RIR206.219.32.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.219.36.0/22No ROA covers it. Add a ROA for AS17570, maxLength 22.672 of 673
Route object: RIR206.219.36.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.219.43.0/24No ROA covers it. Add a ROA for AS17570, maxLength 24.672 of 673
Route object: RIR206.219.43.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.219.44.0/24No ROA covers it. Add a ROA for AS17570, maxLength 24.672 of 673
Route object: RIR206.219.44.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.219.45.0/24No ROA covers it. Add a ROA for AS17570, maxLength 24.672 of 673
Route object: RIR206.219.45.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.219.60.0/22No ROA covers it. Add a ROA for AS17570, maxLength 22.672 of 673
Route object: RIR206.219.60.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

206.219.32.0/21RADBNo ROA
206.219.63.0/24RADBNo ROA
211.104.34.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.