HOZU
BGP inherited
Cluster stats
| Netblocks | 8 |
| Cluster ID | 209190756 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-19
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 82.200.128.140/30 | HOZU | RIPE | ASSIGNED PA | ● low |
| 82.200.131.244/30 | HOZU | RIPE | ASSIGNED PA | ● low |
| 82.200.146.76/30 | HOZU | RIPE | ASSIGNED PA | ● low |
| 87.247.18.168/29 | HOZU-NET | RIPE | ASSIGNED PA | ● low |
| 89.218.32.192/30 | HOZU | RIPE | ASSIGNED PA | ● low |
| 89.218.42.212/30 | HOZU | RIPE | ASSIGNED PA | ● low |
| 89.218.50.100/30 | HOZU | RIPE | ASSIGNED PA | ● low |
| 92.46.55.208/30 | HOZU | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- HOLOHOZU-7-5-2002 sub-allocation
- HOZUPARLAMENTA via JSC Kazakhtelecom sub-allocation
- GUSTEPNOGORSKLESKHOZUPR via JSC Kazakhtelecom sub-allocation
- KGUOTRADUCHLESHOZUPRAKM via JSC Kazakhtelecom sub-allocation
- Hozupravlenie_akimat via JSC Kazakhtelecom sub-allocation
- Hoz Upr Akimat via JSC Kazakhtelecom sub-allocation
Network trust
what's this?
RPKI hygiene: B
how networks compare →
87.5%
of checked blocks have valid RPKI ROA coverage
(7 of 8)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KNIC-MNT
SATELCOM-MNT