Network · data from 2026-11-12
AS24041 VCUSTOMER-INDIA-AS-AP - VCustomer Services India Pvt Ltd. Transit AS.
Registry name: VCUSTOMER-INDIA-AS-AP - VCustomer Services India Pvt Ltd. Transit AS., IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24041, 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.
| 119.92.160.0/24 | Invalid: origin | None | 28 4%low visibility |
AS-SET
AS24041 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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 119.92.160.0/24 | ROAs covering it name AS9299, not AS24041. If AS24041 should announce it, add a ROA for AS24041. |
| Route object: none | 119.92.160.0/24 | No route object for it. Add a route object with origin AS24041 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24041 whose prefix no peer sees AS24041 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.41.205.0/24 | APNIC | No ROA |
| 202.41.206.0/24 | APNIC, RADB | No ROA |
| 202.41.207.0/24 | APNIC, NTTCOM, 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.