HCC

BGP inherited
Cluster stats
Netblocks6
Registered in United Kingdom (3) · India (1) · JO (1)
All fragments 36 blocks across 18 clusters
Cluster ID209098503
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 12 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names 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
31.28.81.104/30 HCC RIPE ASSIGNED PA ● low
111.93.42.216/29 HCC APNIC ALLOCATED NON-PORTABLE ● low
195.11.108.224/27 HCC RIPE ASSIGNED PA ● low
212.113.7.208/29 HCC-International RIPE ASSIGNED PA ● low
213.186.163.152/29 HCC RIPE ASSIGNED PA ● low
2a00:2381:2dce::/48 HCC-INTERNATIONAL RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “HCC” — 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.
Combined view of all 18 name-family clusters →

Network trust

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

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

2a00:2381:2dce::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AI AT1287-AP BTNET-MNT DUMY-RIPE DUMY-RIPE GO-JOR LEVEL3-MNT MAINT-IN-TTSLMEIS QUZAUK TTLC1-AP TTLC1-AP VODAFONE-WORLDWIDE-MNTNER