MAHESH
Data as of 2026-09-06
BGP inherited
This organisation
| Netblocks | 3 · 1,024 IPv4 addresses |
| Also registered under this name | 10 netblocks across 3 separate records |
| Record ID | 240384148 |
| Registry | APNIC |
| Customers | see who runs inside 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 · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.87.90.0/24 | MAHESH | APNIC | ASSIGNED PORTABLE | ● high |
| 103.117.9.0/24 | MAHESH | APNIC | ASSIGNED PORTABLE | ● high |
| 103.220.20.0/23 | MAHESH | APNIC | ASSIGNED PORTABLE | ● high |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
RPKI-inferred operator
SAI NETWORKS
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
AS2222-AP
CO114-AP
MAINT-IN-IRINN
MK1222-AP