Network · data from 2026-11-12
AS147241 SRIDEVIDM-AS-IN - SRIDEVI DIGITAL MEDIA
Registry name: SRIDEVIDM-AS-IN - SRIDEVI DIGITAL MEDIA, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS147241, 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.
| 2.26.189.0/24 | Invalid: origin | None | 1 0%low visibility |
AS-SET
AS147241 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 6 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2.26.189.0/24 | ROAs covering it name AS209693, not AS147241. If AS147241 should announce it, add a ROA for AS147241. |
| Route object: none | 2.26.189.0/24 | No route object for it. Add a route object with origin AS147241 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS147241 whose prefix no peer sees AS147241 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.176.158.0/23 | APNIC | Valid |
| 103.176.158.0/24 | APNIC | Valid |
| 103.176.159.0/24 | APNIC | Valid |
| 2001:df2:cc40::/48 | 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.