HASAN YAVUZ
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 191656578 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2.56.111.0/24 | HASAN YAVUZ | BGP | ANNOUNCED | ● high |
| 2.56.111.0/24 | HASAN YAVUZ | RIPE | SUB-ALLOCATED PA | ● high |
| 2a14:db80:3::/48 | HASAN YAVUZ | RIPE | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (2)
These blocks are registered to HASAN YAVUZ 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.56.111.0/24 /24 | authorized for AS215242 — DATAPENTA LIMITED |
| 2.56.111.0/24 /24 | authorized for AS215242 — DATAPENTA LIMITED |
NIC Handles
ACRO55992-RIPE
AS216045
DATAPENTA-MNT
DATAPENTA-MNT
DUMY-RIPE
DUMY-RIPE
ORG-HY32-RIPE
lir-tr-mgn-1-MNT