Network · data from 2026-11-12
AS146903 VORRUCKEN-AS-IN - VORRUCKEN NETWORKS PRIVATE LIMITED
Registry name: VORRUCKEN-AS-IN - VORRUCKEN NETWORKS PRIVATE LIMITED, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS146903, 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.
| 69.33.208.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 157.254.154.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
AS-SET
AS146903 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 7 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 69.33.208.0/24 | ROAs covering it name AS834, not AS146903. If AS146903 should announce it, add a ROA for AS146903. |
| Route object: none | 69.33.208.0/24 | Route objects for it name AS834. Add a route object with origin AS146903 in the RIR database for the space. |
| ROA: origin | 157.254.154.0/24 | ROAs covering it name AS401142, not AS146903. If AS146903 should announce it, add a ROA for AS146903. |
| Route object: none | 157.254.154.0/24 | Route objects for it name AS401142. Add a route object with origin AS146903 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS146903 whose prefix no peer sees AS146903 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.173.238.0/23 | APNIC | Valid |
| 103.173.238.0/24 | APNIC | Valid |
| 103.173.239.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.