htp GmbH

HTP-INFRA-3
BGP inherited
Cluster stats
Netblocks7
All fragments 46 blocks across 3 clusters
Cluster ID211317968
RegistryRIPE
Customersfind customers using 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

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
212.59.32.0/27 HTP-INFRA-3 RIPE ASSIGNED PA ● low
212.59.32.248/29 HTP-INFRA-3 RIPE ASSIGNED PA ● low
212.59.33.64/27 HTP-INFRA-3 RIPE ASSIGNED PA ● low
212.59.34.112/28 HTP-INFRA-3 RIPE ASSIGNED PA ● low
212.59.34.160/28 HTP-INFRA-3 RIPE ASSIGNED PA ● low
212.59.35.56/29 HTP-INFRA-3 RIPE ASSIGNED PA ● low
212.59.57.8/29 HTP-INFRA-3 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “HTP INFRA” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HTP-MNT