Yanislav Basiuk
Cluster stats
| Netblocks | 30 |
| Cluster ID | 191657400 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 17 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
30
0 netblocks since 2026-07-05
2026-07-05
peak 30
2026-07-06
IP Ranges (30)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.175.134.0/24 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 5.175.236.0/24 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 91.193.111.0/24 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 178.18.227.2/32 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 178.18.237.77/32 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 185.1.184.155/32 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 185.1.215.94/32 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 2001:678:978::/48 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2001:678:978::/48 | Yanislav Basiuk | RIPE | ASSIGNED PI | ● high |
| 2001:7f8:117::200:993:1/128 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:134::9a/128 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::227:2/128 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::237:77/128 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 2a06:de00:a3::/48 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a0d:d940:5e::/48 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a0d:d940:1100::/40 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a0d:d940:1300::/40 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a0d:d940:1f00::/40 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a0e:8f01:1000:9::11b/128 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:62::103/128 | Yanislav Basiuk | PEERINGDB | ASSIGNED | ● high |
| 2a10:ccc1:1333::/48 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a12:4141::/48 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a12:4141:fa00::/40 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a12:4141:fb00::/40 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a14:7583:a000::/38 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a14:7583:e304::/46 | Yanislav Basiuk | BGP | ANNOUNCED | ● high |
| 2a12:4141::/32 | Yanislav Basiuk | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a12:4141:fa00::/40 | Yanislav Basiuk | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a12:4141:fb00::/40 | Yanislav Basiuk | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a12:4141:fc00::/40 | Yanislav Basiuk | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(20 of 30)
Possible discrepancies (1)
These blocks are registered to Yanislav Basiuk 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.
| 5.175.134.0/24 /24 | authorized for AS12586 — GHOSTnet GmbH |
NIC Handles
APNET-MNT
AS199133
AS200993
AS200993
DUMY-RIPE
DUMY-RIPE
GHOSTNET-MNT
I6P-MNT
IP-RIPE
IP-RIPE
ORG-YB31-RIPE
RIPE-NCC-END-MNT
+5 more