bgpreport

Network · data from 2026-11-12

AS17443 KARUTURI-IN - Karuturi Telecom Pvt Ltd

Registry name: KARUTURI-IN - Karuturi Telecom Pvt Ltd, IN · not in PeeringDB

1IPv4 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
58Route objects not announced registered with origin AS17443, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17443, 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.

202.131.159.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS17443 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 58 are in fix.csv.

  • Route object: not announced58

Route objects not announced

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

129.192.240.0/24REACHNo ROA
202.3.112.0/24RADBNo ROA
202.3.120.0/24RADBNo ROA
202.59.2.0/23RADBNo ROA
202.122.16.0/21REACHInvalid: origin
202.131.128.0/19REACHNo ROA
202.131.129.0/24APNICValid
202.131.130.0/24APNICValid
202.131.131.0/24APNICValid
202.131.132.0/24APNICValid
202.131.133.0/24APNICValid
202.131.134.0/24APNICValid
202.131.135.0/24APNICValid
202.131.138.0/24APNICValid
202.131.139.0/24APNICValid
202.131.140.0/24APNICValid
202.131.141.0/24APNICValid
202.131.143.0/24APNICInvalid: origin
202.131.144.0/24APNICValid
202.131.145.0/24APNICValid
202.131.146.0/24APNICValid
202.131.147.0/24APNICValid
202.131.148.0/24APNICValid
202.131.149.0/24APNICValid
202.131.150.0/24APNICValid
202.131.151.0/24APNICValid
202.131.152.0/24APNICValid
202.131.153.0/24APNICValid
202.131.154.0/24APNICValid
202.131.155.0/24APNICValid
202.131.156.0/22RADBNo ROA
202.131.156.0/24APNICValid
202.131.157.0/24APNICValid
202.131.158.0/24APNICValid
202.140.32.0/19APNIC, REACHNo ROA
202.140.32.0/22REACHNo ROA
202.140.33.0/24APNICInvalid: origin
202.140.34.0/24APNICInvalid: origin
202.140.35.0/24APNICInvalid: origin
202.140.36.0/22REACHNo ROA
202.140.36.0/24APNICInvalid: origin
202.140.38.0/24APNICInvalid: origin
202.140.39.0/24APNICInvalid: origin
202.140.45.0/24APNICInvalid: origin
202.140.47.0/24APNICInvalid: origin
202.140.52.0/24APNICInvalid: origin
202.140.53.0/24APNICInvalid: origin
202.140.54.0/24APNICInvalid: origin
202.140.56.0/24APNICInvalid: origin
202.140.57.0/24APNICInvalid: origin
202.140.58.0/24APNICInvalid: origin
202.140.59.0/24APNICInvalid: origin
202.140.60.0/24APNICInvalid: origin
202.140.61.0/24APNICInvalid: origin
202.149.39.0/24REACHNo ROA
202.149.48.0/21REACHNo ROA
203.174.6.0/24REACHInvalid: origin
2001:ca8::/33APNICNo 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.