bgpreport

Network · data from 2026-11-12

AS46004 SKBMIL-KR - SK Broadband Co Ltd

Registry name: SKBMIL-KR - SK Broadband Co Ltd, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46004, 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.
1.224.32.0/20 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS46004 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 23 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none1.224.32.0/20No ROA covers it. Add a ROA for AS46004, maxLength 20.673 of 673
Route object: RIR1.224.32.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

1.228.0.0/15RADBNo ROA
175.122.0.0/18NTTCOMNo ROA
175.122.64.0/20NTTCOMNo ROA
175.122.80.0/21NTTCOMNo ROA
175.122.88.0/24NTTCOMNo ROA
175.122.89.0/24NTTCOMNo ROA
175.122.90.0/24NTTCOMNo ROA
175.122.91.0/24NTTCOMNo ROA
175.122.92.0/22NTTCOMNo ROA
175.122.96.0/19NTTCOMNo ROA
175.122.128.0/17NTTCOMNo ROA
175.123.0.0/20NTTCOMNo ROA
175.123.16.0/24NTTCOMNo ROA
175.123.17.0/24NTTCOMNo ROA
175.123.18.0/24NTTCOMNo ROA
175.123.208.0/20NTTCOMNo ROA
175.123.224.0/21NTTCOMNo ROA
175.123.232.0/22NTTCOMNo ROA
175.123.236.0/24NTTCOMNo ROA
175.123.237.0/24NTTCOMNo ROA
175.123.238.0/24NTTCOMNo 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.