VLADIMIR-PISKUNOV
BGP inherited
Cluster stats
| Netblocks | 15 |
| All fragments | 165 blocks across 39 clusters |
| Cluster ID | 205123912 |
| 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 | |
Footprint over time
4 weekly snapshots · JSON
15
0 netblocks since 2026-07-05
2026-07-05
peak 15
2026-07-13
IP Ranges (15)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 136.243.118.224/29 | VLADIMIR-PISKUNOV | RIPE | LEGACY | ● low |
| 2a01:4f8:120:63ea::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f8:13b:c5f::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f8:150:312f::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f8:190:628a::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f8:212:1490::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f8:212:1b5b::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f8:221:264d::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f8:222:2e50::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f8:241:10d9::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f9:4a:1330::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f9:4a:15d3::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f9:4a:15d4::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f9:4a:15d6::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
| 2a01:4f9:4a:15d8::/64 | VLADIMIR-PISKUNOV | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
93.3%
of checked blocks have valid RPKI ROA coverage
(14 of 15)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
HOS-GUN