ZSCALER-MOSCOW
Cluster stats
| Netblocks | 3 |
| All fragments | 2,594 blocks across 186 clusters |
| Cluster ID | 194005158 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.46.150.0/24 | ZSCALER-MOSCOW | RIPE | ASSIGNED PA | ● low |
| 164.137.100.0/24 | ZSCALER-MOSCOW | RIPE | ASSIGNED PA | ● low |
| 164.137.219.0/24 | ZSCALER-MOSCOW | 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
(3 of 3)
Possible discrepancies (1)
These blocks are registered to ZSCALER-MOSCOW 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.
| 46.46.150.0/24 /24 | authorized for AS29470 — JSC "RetnNet" |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-RETNRU
ZSCALER-RIPE-MNT