Network · data from 2026-11-12
AS149249 RUCHICOM-AS-IN - Ruchi Communication
Registry name: RUCHICOM-AS-IN - Ruchi Communication, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149249, 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.
| 2407:d640::/48 | Invalid: origin | Other origin only | 5 1%low visibility |
| 103.88.126.0/24 | No ROA | None | 673 100% |
| 103.137.194.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.137.195.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.172.154.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.172.155.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS149249 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
- ROA: none1
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2407:d640::/48 | ROAs covering it name AS134006, not AS149249. If AS149249 should announce it, add a ROA for AS149249. |
| Route object: none | 2407:d640::/48 | Route objects for it name AS134006. Add a route object with origin AS149249 in the RIR database for the space. |
| ROA: none | 103.88.126.0/24 | No ROA covers it. Add a ROA for AS149249, maxLength 24. |
| Route object: none | 103.88.126.0/24 | No route object for it. Add a route object with origin AS149249 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS149249 whose prefix no peer sees AS149249 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.137.194.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.