Ercan Alacam
BGP inherited
Cluster stats
| Netblocks | 5 |
| All fragments | 9 blocks across 4 clusters |
| Cluster ID | 191713281 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.198.113.0/24 | Ercan Alacam | BGP | ANNOUNCED | ● high |
| 46.20.97.0/24 | Ercan Alacam | BGP | ANNOUNCED | ● high |
| 87.76.131.0/24 | Ercan Alacam | BGP | ANNOUNCED | ● high |
| 151.242.52.0/24 | Ercan Alacam | BGP | ANNOUNCED | ● high |
| 212.100.185.0/24 | Ercan Alacam | BGP | ANNOUNCED | ● high |
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 Ercan Alacam 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.
| 45.198.113.0/24 /24 | authorized for AS17561 — Larus Limited |
NIC Handles
AS207805
IPBNB-MNT
interlir-mnt
netutils-mnt