NCLHL-CONNECTIVITY
Cluster stats
| Netblocks | 22 |
| Cluster ID | 192559476 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 (22)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.248.106.0/23 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 46.248.124.0/23 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 46.248.126.0/23 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 82.136.7.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.0.0/23 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.2.0/23 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.4.0/23 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.6.0/23 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.8.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.10.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.11.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.12.0/23 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.24.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.28.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.29.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.30.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 85.116.31.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 213.230.214.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 213.230.224.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 213.230.225.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 213.230.248.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
| 213.230.251.0/24 | NCLHL-CONNECTIVITY | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(22 of 22)
Possible discrepancies (22)
These blocks are registered to NCLHL-CONNECTIVITY but cryptographically authorized for a different, unrelated network (3 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 46.248.106.0/23 /23 | authorized for AS2856 — British Telecommunications PLC |
| 46.248.124.0/23 /23 | authorized for AS2856 — British Telecommunications PLC |
| 46.248.126.0/23 /23 | authorized for AS2856 — British Telecommunications PLC |
| 85.116.0.0/23 /23 | authorized for AS2856 — British Telecommunications PLC |
| 85.116.2.0/23 /23 | authorized for AS2856 — British Telecommunications PLC |
| 85.116.4.0/23 /23 | authorized for AS2856 — British Telecommunications PLC |
| 85.116.6.0/23 /23 | authorized for AS2856 — British Telecommunications PLC |
| 85.116.12.0/23 /23 | authorized for AS25098 — Netcalibre Ltd |
| 85.116.24.0/24 /24 | authorized for AS2856 — British Telecommunications PLC |
| 85.116.28.0/24 /24 | authorized for AS3320 — Deutsche Telekom AG |
| 85.116.29.0/24 /24 | authorized for AS3320 — Deutsche Telekom AG |
| 85.116.30.0/24 /24 | authorized for AS3320 — Deutsche Telekom AG |
| 85.116.31.0/24 /24 | authorized for AS3320 — Deutsche Telekom AG |
| 85.116.8.0/24 /24 | authorized for AS25098 — Netcalibre Ltd |
| 213.230.214.0/24 /24 | authorized for AS2856 — British Telecommunications PLC |
+7 more — see the REST API
NIC Handles
BURSTFIRE-MNT
DUMY-RIPE
DUMY-RIPE
LCH-MNT