Network · data from 2026-11-12
AS149208 RAKESSEN-AS-IN - RAKESH TELESOFT
Registry name: RAKESSEN-AS-IN - RAKESH TELESOFT, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149208, 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.
| 196.251.65.0/24 | Invalid: origin | Other origin only | 9 1%low visibility |
| 103.185.163.0/24 | No ROA | Nonecovered by 103.185.162.0/23 | 666 99% |
| 103.185.162.0/24 | No ROA | Nonecovered by 103.185.162.0/23 | 665 99% |
| 103.133.182.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.133.183.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.178.141.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.184.162.0/24 | No ROA | Other IRR onlyRADB | 666 99% |
| 103.184.163.0/24 | No ROA | Other IRR onlyRADB | 666 99% |
| 103.178.140.0/24 | Valid | RIR databaseAPNIC | 671 100% |
AS-SET
AS149208 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 18 are in fix.csv.
- ROA: origin1
- ROA: none7
- Route object: none3
- Route object: RIR5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 196.251.65.0/24 | ROAs covering it name AS29802, not AS149208. If AS149208 should announce it, add a ROA for AS149208. |
| Route object: none | 196.251.65.0/24 | Route objects for it name AS29802. Add a route object with origin AS149208 in the RIR database for the space. |
| ROA: none | 103.185.163.0/24 | No ROA covers it. Add a ROA for AS149208, maxLength 24. |
| Route object: none | 103.185.163.0/24 | No route object for it. A route object for 103.185.162.0/23 with origin AS149208 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149208 in the RIR database for the space. |
| ROA: none | 103.185.162.0/24 | No ROA covers it. Add a ROA for AS149208, maxLength 24. |
| Route object: none | 103.185.162.0/24 | No route object for it. A route object for 103.185.162.0/23 with origin AS149208 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149208 in the RIR database for the space. |
| ROA: none | 103.133.182.0/24 | No ROA covers it. Add a ROA for AS149208, maxLength 24. |
| Route object: RIR | 103.133.182.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.133.183.0/24 | No ROA covers it. Add a ROA for AS149208, maxLength 24. |
| Route object: RIR | 103.133.183.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.178.141.0/24 | No ROA covers it. Add a ROA for AS149208, maxLength 24. |
| Route object: RIR | 103.178.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.184.162.0/24 | No ROA covers it. Add a ROA for AS149208, maxLength 24. |
| Route object: RIR | 103.184.162.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.184.163.0/24 | No ROA covers it. Add a ROA for AS149208, maxLength 24. |
| Route object: RIR | 103.184.163.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS149208 whose prefix no peer sees AS149208 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.185.162.0/23 | RADB | No ROA |
| 103.239.235.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.