bgpreport

Network · data from 2026-11-12

AS17502 KSIL-AS-TW - Kuang Shih International Ltd. Ltd

Registry name: KSIL-AS-TW - Kuang Shih International Ltd. Ltd, TW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17502, 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.
103.136.210.0/23 Valid Other IRR onlyRADB 672 100% 66
103.136.210.0/24 Valid Other IRR onlyRADB 672 100% 66
103.136.211.0/24 Valid Other IRR onlyRADB 666 99% 67

AS-SET

AS17502 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 8 are in fix.csv.

  • Route object: RIR3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR103.136.210.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.136.210.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.136.211.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

203.207.0.0/20NTTCOMNo ROA
203.207.0.0/21NTTCOMNo ROA
203.207.4.0/24NTTCOMNo ROA
203.207.8.0/21NTTCOMNo ROA
203.207.9.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.