CMS-CAMERON-MCKENNA
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 5 |
| IPv6 | 1 prefix (largest 2a00:2381:f664::/48) |
| All fragments | 6 blocks across 2 clusters |
| Cluster ID | 217100809 |
| 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 · report an issue | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.168.17.32/28 | CMS-CAMERON-MCKENNA | RIPE | ASSIGNED PA | ● low |
| 80.168.148.248/29 | CMS-CAMERON-MCKENNA | RIPE | ASSIGNED PA | ● low |
| 195.171.107.216/29 | CMS-CAMERON-MCKENNA | RIPE | ASSIGNED PA | ● low |
| 212.169.34.160/28 | CMS-CAMERON-MCKENNA | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:f664::/48 | CMS-CAMERON-MCKENNA | RIPE | AGGREGATED-BY-LIR | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a00:2381:f664::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (1)
These blocks are registered to CMS-CAMERON-MCKENNA 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:f664::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
AS8426-MNT
BTNET-MNT
DUMY-RIPE
DUMY-RIPE