Rezerv
AB_Rezerv
Registry
Cluster stats
| Netblocks | 5 |
| All fragments | 521 blocks across 235 clusters |
| Cluster ID | 192811072 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2.63.140.0/22 | Rezerv | RIPE | ASSIGNED PA | ● low |
| 95.167.44.20/30 | AB_Rezerv | RIPE | ASSIGNED PA | ● low |
| 95.167.44.152/30 | AB_Rezerv | RIPE | ASSIGNED PA | ● low |
| 95.167.166.4/30 | AB_Rezerv | RIPE | ASSIGNED PA | ● low |
| 188.128.94.124/30 | Rezerv | 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
(5 of 5)
Possible discrepancies (1)
These blocks are registered to Rezerv 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.
| 2.63.140.0/22 /22 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT