bgpreport

Network · data from 2026-11-12

AS18340 SBKOREA

Registry name: SBKOREA-AS-KR-KR - SBKorea, KR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18340, 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.
168.222.17.0/24 Invalid: origin Other origin only 1 0%low visibility 1

AS-SET

AS18340's PeeringDB record names no 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 17 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: origin168.222.17.0/24ROAs covering it name AS44259, not AS18340. If AS18340 should announce it, add a ROA for AS18340.1 of 673
Route object: none168.222.17.0/24Route objects for it name AS44259. Add a route object with origin AS18340 in the RIR database for the space.1 of 673

Route objects not announced

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

103.124.100.0/22APNICValid
103.124.100.0/23APNICValid
103.124.100.0/24APNIC, RADBValid
103.124.101.0/24APNIC, RADBValid
103.124.102.0/23APNICValid
103.124.102.0/24APNIC, RADBValid
103.124.103.0/24APNIC, RADBValid
163.152.240.0/22RADBNo ROA
210.91.3.0/24RADBNo ROA
211.51.40.0/22RADBNo ROA
211.51.40.0/24RADBNo ROA
211.51.41.0/24RADBNo ROA
211.51.42.0/24RADBNo ROA
211.51.43.0/24RADBNo ROA
2400:fda6::/32RADBNo 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.