Network · data from 2026-11-12
AS150042 DSNET-AS-IN - DAINIK SAVERA NET PRIVATE LIMITED
Registry name: DSNET-AS-IN - DAINIK SAVERA NET PRIVATE LIMITED, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150042, 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.
| 38.183.56.0/24 | Invalid: origin | Other origin only | 153 23% |
| 103.190.4.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS150042 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
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 38.183.56.0/24 | ROAs covering it name AS133661, not AS150042. If AS150042 should announce it, add a ROA for AS150042. |
| Route object: none | 38.183.56.0/24 | Route objects for it name AS133661. Add a route object with origin AS150042 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS150042 whose prefix no peer sees AS150042 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.190.4.0/23 | APNIC | Valid |
| 103.190.5.0/24 | APNIC | Valid |
| 2400:8a60::/32 | 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.