Network · data from 2026-11-12
AS9285 IBSPLC-AS-AP - Technopark, Trivandrum, India
Registry name: IBSPLC-AS-AP - Technopark, Trivandrum, India, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9285, 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.177.44.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 202.177.45.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 202.177.46.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 202.177.47.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
AS9285 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 16 are in fix.csv.
- ROA: none4
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.177.44.0/24 | No ROA covers it. Add a ROA for AS9285, maxLength 24. |
| ROA: none | 202.177.45.0/24 | No ROA covers it. Add a ROA for AS9285, maxLength 24. |
| ROA: none | 202.177.46.0/24 | No ROA covers it. Add a ROA for AS9285, maxLength 24. |
| ROA: none | 202.177.47.0/24 | No ROA covers it. Add a ROA for AS9285, maxLength 24. |
Route objects not announced
Route objects with origin AS9285 whose prefix no peer sees AS9285 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.177.46.0/23 | RADB | No ROA |
| 203.13.214.0/24 | RADB | No ROA |
| 203.17.244.0/23 | RADB | No ROA |
| 203.19.156.0/24 | RADB | No ROA |
| 203.25.150.0/24 | RADB | No ROA |
| 203.26.7.0/24 | RADB | No ROA |
| 203.27.117.0/24 | RADB | No ROA |
| 203.30.220.0/24 | RADB | No ROA |
| 203.57.208.0/21 | RADB | No ROA |
| 203.173.0.0/18 | RADB | No ROA |
| 210.8.105.0/24 | RADB | No ROA |
| 210.8.123.0/24 | RADB | No 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.