YASHNET-IN
BGP inherited
Cluster stats
| Netblocks | 6 · 3,066 IPv4 addresses |
| Cluster ID | 210130999 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-19
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.21.232.0/22 | YASHNET-IN | APNIC | ALLOCATED PORTABLE | ● low |
| 103.21.232.0/24 | YASHNET-IN | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 103.21.233.0/24 | YASHNET-IN | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 103.21.234.0/24 | YASHNET-IN | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 103.21.235.0/24 | YASHNET-IN | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 150.129.88.0/22 | YASHNET-IN | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
RPKI-inferred operator
2713/4 lakshmi building adipampa road v.v.mohalla
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
MAINT-IN-IRINN
MAINT-YASHNET-IN
MCNA6-AP
MCNA6-AP