HELHA

BGP inherited
Cluster stats
Netblocks6
Cluster ID208874636
RegistryRIPE
Customersfind 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

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
193.190.66.0/26 HELHA RIPE ASSIGNED PA ● high
193.190.75.16/28 HELHA RIPE ASSIGNED PA ● high
193.190.75.32/29 HELHA RIPE ASSIGNED PA ● high
193.190.75.40/29 HELHA RIPE ASSIGNED PA ● high
193.191.131.0/27 HELHA RIPE ASSIGNED PA ● high
2001:6a8:3480::/48 HELHA RIPE ASSIGNED ● high

Possibly related to this organisation

what's this?
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
Possible discrepancies (1)

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

2001:6a8:3480::/48 /48 authorized for AS2611 — BELNET

NIC Handles

BELNET-MNT DUMY-RIPE DUMY-RIPE HAC58-RIPE