bgpreport

Network · data from 2026-11-12

AS4693 SCSK Corporation

Registry name: CSK - CSK-IT MANAGEMENT CORPORATION, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS4693, 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.
203.140.0.0/19 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
203.179.32.0/19 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
211.7.192.0/21 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
211.7.208.0/21 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
210.159.96.0/19 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
210.166.96.0/19 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
210.249.192.0/19 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
2400:af80::/32 No ROA Other IRR onlyJPIRR, RADB 633 100% 70

AS-SET

AS4693'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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none203.140.0.0/19No ROA covers it. Add a ROA for AS4693, maxLength 19.672 of 673
Route object: RIR203.140.0.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.179.32.0/19No ROA covers it. Add a ROA for AS4693, maxLength 19.672 of 673
Route object: RIR203.179.32.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.7.192.0/21No ROA covers it. Add a ROA for AS4693, maxLength 21.672 of 673
Route object: RIR211.7.192.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.7.208.0/21No ROA covers it. Add a ROA for AS4693, maxLength 21.672 of 673
Route object: RIR211.7.208.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none210.159.96.0/19No ROA covers it. Add a ROA for AS4693, maxLength 19.671 of 673
Route object: RIR210.159.96.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none210.166.96.0/19No ROA covers it. Add a ROA for AS4693, maxLength 19.671 of 673
Route object: RIR210.166.96.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none210.249.192.0/19No ROA covers it. Add a ROA for AS4693, maxLength 19.671 of 673
Route object: RIR210.249.192.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none2400:af80::/32No ROA covers it. Add a ROA for AS4693, maxLength 32.633 of 636
Route object: RIR2400:af80::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS4693 is announced.

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.