bgpreport

Network · data from 2026-11-12

AS38109 SKB-TCNINTERNET-AS-KR-KR - SK Broadband Co Ltd

Registry name: SKB-TCNINTERNET-AS-KR-KR - SK Broadband Co Ltd, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38109, 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.
27.124.128.0/17 No ROA Other IRR onlyRADB 673 100% 67
45.112.156.0/22 No ROA Other IRR onlyRADB 673 100% 67
111.171.0.0/17 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
112.140.64.0/18 No ROA Other IRR onlyRADB 673 100% 67
117.58.128.0/20 No ROA Other IRR onlyRADB 673 100% 67
120.143.160.0/19 No ROA Other IRR onlyRADB 673 100% 67
203.130.176.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67

AS-SET

AS38109 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 74 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced60
ChangePrefix or setDetailFull-table peers
ROA: none27.124.128.0/17No ROA covers it. Add a ROA for AS38109, maxLength 17.673 of 673
Route object: RIR27.124.128.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none45.112.156.0/22No ROA covers it. Add a ROA for AS38109, maxLength 22.673 of 673
Route object: RIR45.112.156.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none111.171.0.0/17No ROA covers it. Add a ROA for AS38109, maxLength 17.673 of 673
Route object: RIR111.171.0.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none112.140.64.0/18No ROA covers it. Add a ROA for AS38109, maxLength 18.673 of 673
Route object: RIR112.140.64.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.58.128.0/20No ROA covers it. Add a ROA for AS38109, maxLength 20.673 of 673
Route object: RIR117.58.128.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none120.143.160.0/19No ROA covers it. Add a ROA for AS38109, maxLength 19.673 of 673
Route object: RIR120.143.160.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.130.176.0/20No ROA covers it. Add a ROA for AS38109, maxLength 20.673 of 673
Route object: RIR203.130.176.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

27.124.128.0/21RADBNo ROA
27.124.128.0/22RADBNo ROA
27.124.136.0/21RADBNo ROA
27.124.140.0/23RADBNo ROA
27.124.144.0/21RADBNo ROA
27.124.148.0/22RADBNo ROA
27.124.160.0/19RADBNo ROA
27.124.160.0/21RADBNo ROA
27.124.168.0/21RADBNo ROA
27.124.168.0/22RADBNo ROA
27.124.176.0/21RADBNo ROA
27.124.184.0/21RADBNo ROA
27.124.184.0/22RADBNo ROA
27.124.192.0/21RADBNo ROA
27.124.200.0/21RADBNo ROA
27.124.204.0/23RADBNo ROA
27.124.206.0/23RADBNo ROA
27.124.208.0/20RADBNo ROA
27.124.216.0/21RADBNo ROA
27.124.216.0/23RADBNo ROA
27.124.218.0/23RADBNo ROA
27.124.232.0/21RADBNo ROA
27.124.237.0/24RADBNo ROA
27.124.244.0/22RADBNo ROA
103.5.128.0/22RADBNo ROA
111.171.0.0/20RADBNo ROA
111.171.16.0/21RADBNo ROA
111.171.24.0/22RADBNo ROA
111.171.28.0/22RADBNo ROA
111.171.32.0/19NTTCOMNo ROA
111.171.32.0/21RADBNo ROA
111.171.40.0/21RADBNo ROA
111.171.64.0/19RADBNo ROA
111.171.64.0/20RADBNo ROA
111.171.64.0/21RADBNo ROA
111.171.80.0/20RADBNo ROA
111.171.124.0/22RADBNo ROA
112.140.64.0/19RADBNo ROA
112.140.64.0/22RADBNo ROA
112.140.80.0/22RADBNo ROA
112.140.84.0/22RADBNo ROA
112.140.88.0/22RADBNo ROA
112.140.96.0/19RADBNo ROA
112.140.96.0/22RADBNo ROA
117.58.128.0/21RADBNo ROA
117.58.136.0/21RADBNo ROA
120.143.160.0/20NTTCOMNo ROA
120.143.162.0/23RADBNo ROA
120.143.168.0/23RADBNo ROA
120.143.170.0/23RADBNo ROA
120.143.172.0/22RADBNo ROA
120.143.176.0/20NTTCOMNo ROA
120.143.176.0/21RADBNo ROA
120.143.184.0/24RADBNo ROA
120.143.185.0/24RADBNo ROA
120.143.186.0/24RADBNo ROA
203.130.176.0/21RADBNo ROA
203.130.176.0/22RADBNo ROA
203.130.182.0/23RADBNo ROA
203.130.184.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.