Network · data from 2026-11-12
AS132322 GDRPL-IN - Good Domain Registry Private Limited
Registry name: GDRPL-IN - Good Domain Registry Private Limited, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132322, 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.14.120.0/24 | No ROA | Nonecovered by 103.14.120.0/22 | 672 100% |
| 103.14.121.0/24 | No ROA | Nonecovered by 103.14.120.0/22 | 672 100% |
| 103.14.122.0/24 | No ROA | Nonecovered by 103.14.120.0/22 | 672 100% |
| 103.14.123.0/24 | No ROA | Nonecovered by 103.14.120.0/22 | 672 100% |
| 103.91.186.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.91.187.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.169.176.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.169.177.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 163.128.112.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 163.128.113.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS132322 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 12 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.14.120.0/24 | No ROA covers it. Add a ROA for AS132322, maxLength 24. |
| Route object: none | 103.14.120.0/24 | No route object for it. A route object for 103.14.120.0/22 with origin AS132322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132322 in the RIR database for the space. |
| ROA: none | 103.14.121.0/24 | No ROA covers it. Add a ROA for AS132322, maxLength 24. |
| Route object: none | 103.14.121.0/24 | No route object for it. A route object for 103.14.120.0/22 with origin AS132322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132322 in the RIR database for the space. |
| ROA: none | 103.14.122.0/24 | No ROA covers it. Add a ROA for AS132322, maxLength 24. |
| Route object: none | 103.14.122.0/24 | No route object for it. A route object for 103.14.120.0/22 with origin AS132322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132322 in the RIR database for the space. |
| ROA: none | 103.14.123.0/24 | No ROA covers it. Add a ROA for AS132322, maxLength 24. |
| Route object: none | 103.14.123.0/24 | No route object for it. A route object for 103.14.120.0/22 with origin AS132322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132322 in the RIR database for the space. |
| ROA: none | 103.91.186.0/24 | No ROA covers it. Add a ROA for AS132322, maxLength 24. |
| ROA: none | 103.91.187.0/24 | No ROA covers it. Add a ROA for AS132322, maxLength 24. |
Route objects not announced
Route objects with origin AS132322 whose prefix no peer sees AS132322 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.14.120.0/22 | APNIC | No ROA |
| 103.169.176.0/23 | APNIC | Valid |
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.