HPC-GEARS
BGP inherited
Cluster stats
| Netblocks | 4 |
| Cluster ID | 210011854 |
| Registry | RIPE |
| Customers | find 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 81.187.94.128/27 | HPC-GEARS | RIPE | ASSIGNED PA | ● low |
| 81.187.95.159/32 | HPC-GEARS | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:ce85::/48 | HPC-GEARS | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:ce85::/56 | HPC-GEARS | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to HPC-GEARS 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:ce85::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
| 2a00:2381:ce85::/56 /56 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
AA
BTNET-MNT
DUMY-RIPE
DUMY-RIPE