bgpreport

Network · data from 2026-11-12

AS59169 KNGD INFOSYS

Registry name: KNDG-AS - KNGD INFOSYS PVT LTD, IN · PeeringDB

8IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
12Route objects not announced registered with origin AS59169, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59169, 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.254.56.0/24 No ROA RIR databaseAPNIC 673 100% 66
103.254.57.0/24 No ROA RIR databaseAPNIC 673 100% 66
103.254.58.0/24 No ROA RIR databaseAPNIC 673 100% 66
103.254.59.0/24 No ROA RIR databaseAPNIC 673 100% 66
157.119.224.0/24 No ROA RIR databaseAPNIC 673 100% 66
157.119.225.0/24 No ROA RIR databaseAPNIC 673 100% 66
157.119.226.0/24 No ROA RIR databaseAPNIC 673 100% 66
157.119.227.0/24 No ROA RIR databaseAPNIC 673 100% 66

AS-SET

AS59169'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 20 are in fix.csv.

  • ROA: none8
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none103.254.56.0/24No ROA covers it. Add a ROA for AS59169, maxLength 24.673 of 673
ROA: none103.254.57.0/24No ROA covers it. Add a ROA for AS59169, maxLength 24.673 of 673
ROA: none103.254.58.0/24No ROA covers it. Add a ROA for AS59169, maxLength 24.673 of 673
ROA: none103.254.59.0/24No ROA covers it. Add a ROA for AS59169, maxLength 24.673 of 673
ROA: none157.119.224.0/24No ROA covers it. Add a ROA for AS59169, maxLength 24.673 of 673
ROA: none157.119.225.0/24No ROA covers it. Add a ROA for AS59169, maxLength 24.673 of 673
ROA: none157.119.226.0/24No ROA covers it. Add a ROA for AS59169, maxLength 24.673 of 673
ROA: none157.119.227.0/24No ROA covers it. Add a ROA for AS59169, maxLength 24.673 of 673

Route objects not announced

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

103.124.240.0/22APNICValid
103.124.240.0/23APNICValid
103.124.240.0/24APNICValid
103.124.241.0/24APNICValid
103.124.242.0/23APNICValid
103.124.242.0/24APNICValid
103.124.243.0/24APNICValid
103.254.56.0/23APNICNo ROA
103.254.58.0/23APNICNo ROA
157.119.224.0/22APNICNo ROA
157.119.224.0/23APNICNo ROA
157.119.226.0/23APNICNo 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.