HT-v6

Data as of 2026-08-30
BGP inherited
This organisation
Netblocks5
IPv6 5 prefixes (largest 2a00:c30:7000::/36)
Record ID235032258
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
2a00:c30:7000::/36 HT-v6 RIPE ALLOCATED-BY-LIR ● low
2a00:c30:7100::/40 HT-v6 RIPE AGGREGATED-BY-LIR ● low
2a00:c30:7200::/40 HT-v6 RIPE AGGREGATED-BY-LIR ● low
2a00:c30:7300::/40 HT-v6 RIPE AGGREGATED-BY-LIR ● low
2a00:c30:7400::/40 HT-v6 RIPE AGGREGATED-BY-LIR ● low

IPv6 ranges (5)

CIDR
2a00:c30:7000::/36
2a00:c30:7100::/40
2a00:c30:7200::/40
2a00:c30:7300::/40
2a00:c30:7400::/40

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (5 of 5)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HPT-MNT