bgpreport

Network · data from 2026-11-12

AS150654 KENNIESIT-AS-IN - Kennies Star India Private Limited

Registry name: KENNIESIT-AS-IN - Kennies Star India Private Limited, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS150654, 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.
149.100.95.0/24 Invalid: origin None 136 20% 53
38.225.204.0/24 No ROA Other IRR onlyRADB 452 67% 63
38.225.205.0/24 No ROA Other IRR onlyRADB 452 67% 63
38.225.206.0/24 No ROA Other IRR onlyRADB 452 67% 63
160.30.206.0/24 No ROA RIR databaseAPNIC 673 100% 66
160.30.207.0/24 No ROA RIR databaseAPNIC 673 100% 66
2401:eba0::/32 No ROA RIR databaseAPNIC 636 100% 70
87.76.165.0/24 Valid RIR databaseRIPE 673 100% 66
103.168.173.0/24 Valid RIR databaseAPNIC 673 100% 66
175.111.97.0/24 Valid RIR databaseAPNIC 673 100% 66

AS-SET

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

  • ROA: origin1
  • ROA: none6
  • Route object: none1
  • Route object: RIR3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin149.100.95.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS150654 should announce it, add a ROA for AS150654.136 of 673
Route object: none149.100.95.0/24No route object for it. Add a route object with origin AS150654 in the RIR database for the space.136 of 673
ROA: none38.225.204.0/24No ROA covers it. Add a ROA for AS150654, maxLength 24.452 of 673
Route object: RIR38.225.204.0/24Route object only in RADB. Add it in the RIR database for the space.452 of 673
ROA: none38.225.205.0/24No ROA covers it. Add a ROA for AS150654, maxLength 24.452 of 673
Route object: RIR38.225.205.0/24Route object only in RADB. Add it in the RIR database for the space.452 of 673
ROA: none38.225.206.0/24No ROA covers it. Add a ROA for AS150654, maxLength 24.452 of 673
Route object: RIR38.225.206.0/24Route object only in RADB. Add it in the RIR database for the space.452 of 673
ROA: none160.30.206.0/24No ROA covers it. Add a ROA for AS150654, maxLength 24.673 of 673
ROA: none160.30.207.0/24No ROA covers it. Add a ROA for AS150654, maxLength 24.673 of 673
ROA: none2401:eba0::/32No ROA covers it. Add a ROA for AS150654, maxLength 32.636 of 636

Route objects not announced

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

38.225.204.0/22RADBNo ROA
38.225.207.0/24RADBNo ROA
103.142.198.0/24APNICValid
103.155.147.0/24APNICValid
2a13:9500:a3::/48RIPEValid

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.