Network · data from 2026-11-12
AS135222 MWNASHIK-AS - MilesWeb Internet Services Pvt Ltd
Registry name: MWNASHIK-AS - MilesWeb Internet Services Pvt Ltd, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135222, 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.
| 45.195.159.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 103.86.176.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.195.243.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 103.86.177.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 103.212.120.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 103.212.121.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 45.195.229.0/24 | Valid | RIR databaseAFRINIC, RADB | 666 99% |
AS-SET
AS135222 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 2 are in fix.csv.
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.195.159.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135222 whose prefix no peer sees AS135222 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.212.120.0/23 | APNIC | 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.