Network · data from 2026-11-12
AS136368 RSPL-AS - Rathnaa Spectra Private Limited
Registry name: RSPL-AS - Rathnaa Spectra Private Limited, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136368, 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.89.64.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.89.64.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.89.65.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.89.66.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.89.66.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.89.67.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df1:2480::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 103.89.64.0/22 | Valid | RIR databaseAPNIC | 40 6%low visibility |
AS-SET
AS136368 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS136368 is announced.
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.