HDS
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 32 blocks across 10 clusters |
| Cluster ID | 193054595 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.226.122.232/29 | HDS | RIPE | ASSIGNED PA | ● low |
| 37.128.98.240/29 | HDS | RIPE | ASSIGNED PA | ● low |
| 194.179.109.47/32 | HdS | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:fa8b::/48 | HDS | RIPE | AGGREGATED-BY-LIR | ● 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 (1)
These blocks are registered to HDS 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:fa8b::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
MAINT-AS3352
NETIA-MNT