BT-HCS-App

BGP inherited
Cluster stats
Netblocks8 · 2,680 IPv4 addresses
All fragments 17 blocks across 2 clusters
Cluster ID210465495
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.7.34.0/23 BT-HCS-APP RIPE ASSIGNED PA ● low
81.128.252.0/23 BT-HCS-App RIPE ASSIGNED PA ● low
109.144.112.192/26 BT-HCS-App RIPE ASSIGNED PA ● low
109.144.116.0/22 BT-HCS-APP RIPE ASSIGNED PA ● low
195.171.237.128/26 BT-HCS-APP RIPE ASSIGNED PA ● low
213.120.138.0/25 BT-HCS-App RIPE ASSIGNED PA ● low
213.120.138.128/25 BT-HCS-App RIPE ASSIGNED PA ● low
213.120.140.0/24 BT-HCS-App RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “BT HCS” — 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.

Network trust

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

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE