jambit GmbH
GLEIF verified
LEI
3912005AEKW5IK5EAH41
Registered name
jambit GmbH
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 6 |
| Cluster ID | 191643862 |
| Registry | RIPE |
| Owner jurisdiction | DE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 3912005AEKW5IK5EAH41 |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-06
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.84.72.0/22 | jambit GmbH | RIPE | ALLOCATED PA | ● low |
| 45.84.72.0/23 | jambit GmbH | RIPE | ASSIGNED PA | ● low |
| 45.84.74.0/23 | jambit GmbH | RIPE | ASSIGNED PA | ● low |
| 2a0e:a680::/32 | jambit GmbH | RIPE | ALLOCATED-BY-RIR | ● low |
| 2a0e:a680::/48 | jambit GmbH | RIPE | ASSIGNED | ● low |
| 2a0e:a680:1::/48 | jambit GmbH | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
Possible discrepancies (4)
These blocks are registered to jambit GmbH 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.
| 2a0e:a680::/48 /48 | authorized for AS8767 — M-net Telekommunikations GmbH |
| 2a0e:a680:1::/48 /48 | authorized for AS8767 — M-net Telekommunikations GmbH |
| 45.84.72.0/23 /23 | authorized for AS8767 — M-net Telekommunikations GmbH |
| 45.84.74.0/23 /23 | authorized for AS8767 — M-net Telekommunikations GmbH |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ORG-JG76-RIPE
RIPE-NCC-HM-MNT
mnt-de-jambit-muc-1