Network · data from 2026-11-12
AS45433 Kappa Internet Services
Registry name: KISPL-AS-IN - Kappa Internet Services Private Limited, IN · PeeringDB
57IPv4 routes
93.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
4No ROA
0 with no route object for this origin
7Low visibility
seen by under 10% of full-table peers
41Route objects not announced
registered with origin AS45433, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS45433, 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.
| 122.102.26.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 45.250.168.0/24 | No ROA | RIR databaseAPNIC, RADB | 671 100% |
| 45.64.178.0/24 | No ROA | RIR databaseAPNIC, RADB | 1 0%low visibility |
| 103.58.249.0/24 | No ROA | RIR databaseAPNIC, RADB | 1 0%low visibility |
| 103.23.236.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.23.237.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.23.238.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.36.49.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.36.50.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.36.51.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.39.8.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.39.9.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.39.10.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.39.11.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.58.248.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.58.251.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.196.210.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.196.211.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.209.176.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.209.177.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.209.178.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.255.8.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.255.10.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 115.178.96.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 115.178.97.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 115.178.99.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 115.178.100.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 115.178.101.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 115.178.102.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 115.178.103.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 122.102.24.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 122.102.25.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 122.102.27.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 122.102.28.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 122.102.29.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 122.102.30.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 122.102.31.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.53.80.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.53.81.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.53.82.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.53.83.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.64.176.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.118.204.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.118.206.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.118.207.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.127.220.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.127.221.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.127.222.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.127.223.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.250.169.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.250.170.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.250.171.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 43.229.74.0/24 | Valid | RIR databaseAPNIC, RADB | 1 0%low visibility |
| 45.64.177.0/24 | Valid | RIR databaseAPNIC, RADB | 1 0%low visibility |
| 45.64.179.0/24 | Valid | RIR databaseAPNIC, RADB | 1 0%low visibility |
| 45.118.205.0/24 | Valid | RIR databaseAPNIC, RADB | 1 0%low visibility |
| 103.58.250.0/24 | Valid | RIR databaseAPNIC, RADB | 1 0%low visibility |
AS-SET
AS45433'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 45 are in fix.csv.
- ROA: none4
- Route object: not announced41
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 122.102.26.0/24 | No ROA covers it. Add a ROA for AS45433, maxLength 24. |
| ROA: none | 45.250.168.0/24 | No ROA covers it. Add a ROA for AS45433, maxLength 24. |
| ROA: none | 45.64.178.0/24 | No ROA covers it. Add a ROA for AS45433, maxLength 24. |
| ROA: none | 103.58.249.0/24 | No ROA covers it. Add a ROA for AS45433, maxLength 24. |
Route objects not announced
Route objects with origin AS45433 whose prefix no peer sees AS45433 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.229.72.0/22 | APNIC | No ROA |
| 43.229.72.0/24 | APNIC, RADB | No ROA |
| 43.229.73.0/24 | APNIC, RADB | Valid |
| 43.229.75.0/24 | APNIC, RADB | No ROA |
| 45.64.176.0/22 | APNIC | No ROA |
| 45.118.204.0/22 | APNIC | No ROA |
| 45.127.220.0/22 | APNIC | No ROA |
| 45.250.168.0/22 | APNIC | No ROA |
| 103.23.236.0/22 | APNIC | No ROA |
| 103.23.239.0/24 | APNIC, RADB | Valid |
| 103.36.48.0/22 | APNIC | No ROA |
| 103.36.48.0/24 | APNIC | Invalid: origin |
| 103.39.8.0/22 | APNIC | No ROA |
| 103.58.248.0/22 | APNIC | No ROA |
| 103.70.58.0/24 | APNIC | Valid |
| 103.157.124.0/24 | APNIC | Valid |
| 103.157.125.0/24 | APNIC | Valid |
| 103.157.168.0/24 | APNIC | Valid |
| 103.157.169.0/24 | APNIC | Valid |
| 103.175.9.0/24 | APNIC | Valid |
| 103.194.120.0/24 | APNIC | Valid |
| 103.196.208.0/22 | APNIC | No ROA |
| 103.196.208.0/24 | APNIC, RADB | Valid |
| 103.196.209.0/24 | APNIC, RADB | Valid |
| 103.207.168.0/24 | APNIC | Valid |
| 103.207.169.0/24 | APNIC | Valid |
| 103.207.170.0/24 | APNIC | Valid |
| 103.207.171.0/24 | APNIC | Valid |
| 103.209.176.0/22 | APNIC | No ROA |
| 103.209.179.0/24 | APNIC, RADB | Valid |
| 103.255.11.0/24 | APNIC, RADB | Valid |
| 115.178.96.0/21 | RADB | No ROA |
| 115.178.96.0/22 | RADB | No ROA |
| 115.178.98.0/24 | APNIC, RADB | Valid |
| 122.102.24.0/21 | APNIC | No ROA |
| 163.53.80.0/22 | APNIC | Valid |
| 175.111.128.0/24 | APNIC | Valid |
| 175.111.129.0/24 | APNIC | Valid |
| 175.111.130.0/24 | APNIC | Valid |
| 175.111.131.0/24 | APNIC | Valid |
| 2400:9080::/32 | APNIC | No 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.