bgpreport

Network · data from 2026-11-12

AS152586 Kuroit (India)

Registry name: KUROIT-AS-AP - Kuroit, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152586, 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.
201.78.131.0/24 Valid None 673 100% 67
185.165.154.0/24 Valid None 672 100% 66
201.78.128.0/24 Valid None 671 100% 67
201.78.132.0/24 Valid None 671 100% 67
103.244.226.0/24 Valid RIR databaseAPNIC 673 100% 67
109.69.111.0/24 Valid RIR databaseRIPE 673 100% 67
163.52.56.0/24 Valid RIR databaseAPNIC 673 100% 66
163.52.57.0/24 Valid RIR databaseAPNIC 673 100% 66
178.239.171.0/24 Valid RIR databaseRIPE 673 100% 67
185.121.26.0/24 Valid RIR databaseRIPE 673 100% 66
185.149.26.0/24 Valid RIR databaseRIPE 673 100% 67
193.176.28.0/24 Valid RIR databaseRIPE 673 100% 67
194.5.147.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
201.78.129.0/24 Valid RIR databaseRIPE 673 100% 67
216.180.126.0/24 Valid RIR databaseARIN 673 100% 67
2.58.201.0/24 Valid RIR databaseRIPE 672 100% 67
2.58.202.0/24 Valid RIR databaseRIPE 672 100% 67
45.11.231.0/24 Valid RIR databaseRIPE 672 100% 66
45.67.84.0/24 Valid RIR databaseRIPE 672 100% 67
185.149.24.0/24 Valid RIR databaseRIPE 672 100% 66
185.149.27.0/24 Valid RIR databaseRIPE 672 100% 66
185.172.38.0/24 Valid RIR databaseRIPE 672 100% 66
185.172.39.0/24 Valid RIR databaseRIPE 672 100% 66
31.59.118.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
185.121.27.0/24 Valid RIR databaseRIPE 671 100% 67
185.149.25.0/24 Valid RIR databaseRIPE 671 100% 67
185.187.155.0/24 Valid RIR databaseRIPE 671 100% 67
216.180.127.0/24 Valid RIR databaseARIN 671 100% 67
2.58.200.0/24 Valid RIR databaseRIPE 670 100% 67
45.67.87.0/24 Valid RIR databaseRIPE 670 100% 67
45.11.230.0/24 Valid RIR databaseRIPE 668 99% 66
216.180.124.0/24 Valid RIR databaseARIN 668 99% 67
2401:8360:a2::/48 Valid RIR databaseAPNIC 636 100% 67
2401:8360:a400::/48 Valid RIR databaseAPNIC 636 100% 70
2401:8360:2::/48 Valid RIR databaseAPNIC 635 100% 69
2401:8360:c::/48 Valid RIR databaseAPNIC 635 100% 67
2401:8360:e::/48 Valid RIR databaseAPNIC 635 100% 69
2401:8360:d::/48 Valid RIR databaseAPNIC 634 100% 70
2401:8360:a1::/48 Valid RIR databaseAPNIC 634 100% 69
2401:8360:a5::/48 Valid RIR databaseAPNIC 634 100% 67

AS-SET

AS152586'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 11 are in fix.csv.

  • Route object: none4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none201.78.131.0/24No route object for it. Add a route object with origin AS152586 in the RIR database for the space.673 of 673
Route object: none185.165.154.0/24No route object for it. Add a route object with origin AS152586 in the RIR database for the space.672 of 673
Route object: none201.78.128.0/24No route object for it. Add a route object with origin AS152586 in the RIR database for the space.671 of 673
Route object: none201.78.132.0/24No route object for it. Add a route object with origin AS152586 in the RIR database for the space.671 of 673

Route objects not announced

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

163.52.56.0/23APNICValid
185.149.24.0/23RIPEValid
185.149.26.0/23RIPEValid
185.172.38.0/23RIPEValid
185.216.72.0/24RIPEValid
2401:8360:6::/48APNICValid
2401:8360:b::/48APNICValid

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.