bgpreport

Network · data from 2026-11-12

AS23578 SKB-NAMDONGNET-AS-KR-KR - SK Broadband Co Ltd

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23578, 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.120.0.0/18 No ROA Other IRR onlyRADB 673 100% 67
45.112.96.0/22 No ROA Other IRR onlyRADB 673 100% 67
103.51.176.0/22 No ROA Other IRR onlyRADB 673 100% 67
124.28.0.0/17 No ROA Other IRR onlyRADB 673 100% 67
124.28.128.0/18 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS23578 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 38 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: none27.120.0.0/18No ROA covers it. Add a ROA for AS23578, maxLength 18.673 of 673
Route object: RIR27.120.0.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none45.112.96.0/22No ROA covers it. Add a ROA for AS23578, maxLength 22.673 of 673
Route object: RIR45.112.96.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.51.176.0/22No ROA covers it. Add a ROA for AS23578, maxLength 22.673 of 673
Route object: RIR103.51.176.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none124.28.0.0/17No ROA covers it. Add a ROA for AS23578, maxLength 17.673 of 673
Route object: RIR124.28.0.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none124.28.128.0/18No ROA covers it. Add a ROA for AS23578, maxLength 18.673 of 673
Route object: RIR124.28.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

27.120.0.0/20NTTCOM, RADBNo ROA
27.120.16.0/20NTTCOM, RADBNo ROA
27.120.32.0/20NTTCOM, RADBNo ROA
27.120.41.0/24RADBNo ROA
27.120.48.0/20NTTCOM, RADBNo ROA
45.112.96.0/23RADBNo ROA
45.112.98.0/23RADBNo ROA
103.51.176.0/23RADBNo ROA
103.51.178.0/23RADBNo ROA
124.28.0.0/20RADBNo ROA
124.28.16.0/20RADBNo ROA
124.28.32.0/20RADBNo ROA
124.28.48.0/20RADBNo ROA
124.28.64.0/20RADBNo ROA
124.28.80.0/20RADBNo ROA
124.28.96.0/20RADBNo ROA
124.28.112.0/20RADBNo ROA
124.28.128.0/20RADBNo ROA
124.28.133.0/24RADBNo ROA
124.28.134.0/24RADBNo ROA
124.28.135.0/24RADBNo ROA
124.28.136.0/24RADBNo ROA
124.28.137.0/24RADBNo ROA
124.28.138.0/24RADBNo ROA
124.28.139.0/24RADBNo ROA
124.28.144.0/20RADBNo ROA
124.28.160.0/20RADBNo ROA
124.28.176.0/20RADBNo 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.