ZHIGUL
BGP inherited
Cluster stats
| Netblocks | 8 · 1,912 IPv4 addresses |
| Cluster ID | 208858673 |
| 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 | 1 distinct registrant name 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 |
|---|---|---|---|---|
| 62.213.6.32/27 | ZHIGUL | RIPE | ASSIGNED PA | ● low |
| 62.213.10.32/27 | ZHIGUL | RIPE | ASSIGNED PA | ● low |
| 62.213.10.96/27 | ZHIGUL | RIPE | ASSIGNED PA | ● low |
| 85.112.49.0/24 | ZHIGUL | RIPE | ASSIGNED PA | ● low |
| 88.200.131.0/24 | ZHIGUL | RIPE | ASSIGNED PA | ● low |
| 88.200.161.0/24 | ZHIGUL | RIPE | ASSIGNED PA | ● low |
| 88.200.204.0/22 | ZHIGUL | RIPE | ASSIGNED PA | ● low |
| 212.32.202.96/27 | ZHIGUL | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(8 of 8)
Possible discrepancies (4)
These blocks are registered to ZHIGUL 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.
| 88.200.204.0/22 /22 | authorized for AS12389 — PJSC Rostelecom |
| 85.112.49.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 88.200.131.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 88.200.161.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSNIIROS-MNT
SAMTEL-MNT