AKIMAT_SUZAK_RAYON
BGP inherited
Cluster stats
| Netblocks | 5 |
| All fragments | 6 blocks across 2 clusters |
| Cluster ID | 204808626 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 88.204.225.32/30 | AKIMAT_SUZAK_RAYON | RIPE | ASSIGNED PA | ● low |
| 89.218.152.64/30 | AKIMAT_SUZAK_RAYON | RIPE | ASSIGNED PA | ● low |
| 89.218.152.68/30 | AKIMAT_SUZAK_RAYON | RIPE | ASSIGNED PA | ● low |
| 89.218.152.72/30 | AKIMAT_SUZAK_RAYON | RIPE | ASSIGNED PA | ● low |
| 89.218.152.84/30 | AKIMAT_SUZAK_RAYON | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “AKIMAT SUZAK” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- AKIMAT_SUZAK 1 blocks
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.
- AKIMAT_SUZAK via JSC Kazakhtelecom sub-allocation
- AKIMATSUZAKSHU via JSC Kazakhtelecom sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KNIC-MNT