CH-THREEMA-L1-6-1
Data as of 2026-07-26
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2a14:3e40::/32) |
| Cluster ID | 216279619 |
| Registry | RIPE |
| Customers | find 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 · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a14:3e40::/32 | CH-THREEMA-L1-6-1 | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a14:3e44::/32 | CH-THREEMA-L2-6-1 | RIPE | ALLOCATED-BY-LIR | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to CH-THREEMA-L1-6-1 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.
| 2a14:3e44::/32 /32 | authorized for AS15576 — NTS workspace AG |
NIC Handles
DUMY-RIPE
DUMY-RIPE
lir-ch-threema-1-MNT