KAOPUCLOUD-BR
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 510 IPv4 addresses |
| Cluster ID | 211067930 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 194.26.73.0/24 | KAOPUCLOUD-BR | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 194.110.135.0/24 | KAOPUCLOUD-BR | RIPE | ASSIGNED PA | ● low |
| 2404:a140:7::/48 | KAOPUCLOUD-BR | APNIC | ALLOCATED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to KAOPUCLOUD-BR but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2404:a140:7::/48 /48 | authorized for AS138195 — MOACK.Co.LTD |
NIC Handles
AK1084-AP
DUMY-RIPE
DUMY-RIPE
KCHL1-AP
KCHL1-AP
MAINT-KAOPU-HK
mnt-hk-kaopu-2