Network · data from 2026-11-12
AS204307 RISHIKESHAN Rishikeshan Lavakumar
Registry name: RISHIKESHAN Rishikeshan Lavakumar, LK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204307, 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.
| 2a06:e881:4320::/46 | No ROA | None | 242 38% |
| 2001:678:638::/48 | Valid | RIR databaseRIPE | 243 38% |
AS-SET
AS204307 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 12 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a06:e881:4320::/46 | No ROA covers it. Add a ROA for AS204307, maxLength 46. |
| Route object: none | 2a06:e881:4320::/46 | No route object for it. Add a route object with origin AS204307 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS204307 whose prefix no peer sees AS204307 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0e:b107:ac0::/48 | RIPE | No ROA |
| 2a0e:b107:ac2::/48 | RIPE | No ROA |
| 2a0f:e401:110::/44 | RIPE | No ROA |
| 2a0f:e401:110::/48 | RIPE | No ROA |
| 2a0f:e401:111::/48 | RIPE | No ROA |
| 2a0f:e401:113::/48 | RIPE | No ROA |
| 2a0f:e401:116::/48 | RIPE | No ROA |
| 2a0f:e401:118::/48 | RIPE | No ROA |
| 2a0f:e401:11a::/48 | RIPE | No ROA |
| 2a0f:e401:11c::/48 | RIPE | 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.