Network · data from 2026-11-12
AS23994 TRANSWORKS-TRANSIT-AS-AP - Concentrix Services India Private Limited
Registry name: TRANSWORKS-TRANSIT-AS-AP - Concentrix Services India Private Limited, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23994, 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.
| 203.32.5.0/24 | No ROA | Nonecovered by 203.32.4.0/23 | 673 100% |
| 203.32.4.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS23994 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 10 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.32.5.0/24 | No ROA covers it. Add a ROA for AS23994, maxLength 24. |
| Route object: none | 203.32.5.0/24 | No route object for it. A route object for 203.32.4.0/23 with origin AS23994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23994 in the RIR database for the space. |
| ROA: none | 203.32.4.0/24 | No ROA covers it. Add a ROA for AS23994, maxLength 24. |
| Route object: RIR | 203.32.4.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23994 whose prefix no peer sees AS23994 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.32.4.0/23 | APNIC, RADB | No ROA |
| 203.32.248.0/23 | RADB | No ROA |
| 203.82.4.0/22 | APNIC | No ROA |
| 203.82.4.0/24 | RADB | No ROA |
| 203.82.248.0/23 | NTTCOM, RADB | No ROA |
| 203.82.249.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.