Network · data from 2026-11-12
AS136332 ADRIINFO-AS - Adri Infocom Pvt Ltd
Registry name: ADRIINFO-AS - Adri Infocom Pvt Ltd, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136332, 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.
| 2405:2540::/32 | No ROA | RIR databaseAPNIC | 635 100% |
| 103.89.56.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.190.252.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.89.58.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.89.59.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.89.56.0/24 | Valid | RIR databaseAPNIC | 3 0%low visibility |
| 103.89.57.0/24 | Valid | RIR databaseAPNIC | 3 0%low visibility |
| 103.190.252.0/24 | Valid | RIR databaseAPNIC | 3 0%low visibility |
| 103.190.253.0/24 | Valid | RIR databaseAPNIC | 3 0%low visibility |
AS-SET
AS136332 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 3 are in fix.csv.
- ROA: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2405:2540::/32 | No ROA covers it. Add a ROA for AS136332, maxLength 32. |
Route objects not announced
Route objects with origin AS136332 whose prefix no peer sees AS136332 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.89.56.0/22 | APNIC, RADB | Valid |
| 103.89.58.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.