HU-EKABEL

Data as of 2026-11-01
BGP inherited
This organisation
Netblocks5 · 608 IPv4 addresses
Record ID259894344
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
109.61.10.0/27 HU-EKABEL RIPE ASSIGNED PA ● low
109.61.26.0/24 HU-EKABEL RIPE ASSIGNED PA ● low
109.61.76.0/24 HU-EKABEL RIPE ASSIGNED PA ● low
109.61.97.0/27 HU-EKABEL RIPE ASSIGNED PA ● low
109.61.97.32/27 HU-EKABEL 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 (2)

These blocks are registered to HU-EKABEL 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.

109.61.76.0/24 /24 authorized for AS197248 — Dravanet Co Ltd.
109.61.26.0/24 /24 authorized for AS197248 — Dravanet Co Ltd.

NIC Handles

DRAVANET-MNT DUMY-RIPE DUMY-RIPE