Network · data from 2026-11-12
AS134301 NDDR-AS-IN - Nddr Infotech Pvt.ltd.
Registry name: NDDR-AS-IN - Nddr Infotech Pvt.ltd., IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134301, 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.88.56.0/24 | No ROA | Other origin only | 1 0%low visibility |
| 103.88.57.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.88.58.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS134301 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 4 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.88.56.0/24 | No ROA covers it. Add a ROA for AS134301, maxLength 24. |
| Route object: none | 103.88.56.0/24 | Route objects for it name AS58762, AS135731. Add a route object with origin AS134301 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS134301 whose prefix no peer sees AS134301 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.88.58.0/23 | APNIC | Valid |
| 103.88.59.0/24 | 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.