JENA

BGP inherited
Cluster stats
Netblocks8
Registered in Czechia (6) · Germany (2)
All fragments 14 blocks across 5 clusters
Cluster ID208826385
RegistryRIPE
Customersfind 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

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.100.0.136/30 JENA RIPE ASSIGNED PA ● low
82.113.38.148/30 JENA RIPE ASSIGNED PA ● low
95.80.214.36/30 JENA RIPE ASSIGNED PA ● low
195.37.112.128/25 JENA-NET RIPE ASSIGNED PA ● low
212.12.56.168/29 JENA-NET RIPE ASSIGNED PA ● low
212.24.151.140/30 JENA RIPE ASSIGNED PA ● low
212.24.158.248/30 JENA RIPE ASSIGNED PA ● low
213.151.82.104/30 JENA RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “JENA” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DFN-LIR-MNT DIALTELECOM-MNT DUMY-RIPE DUMY-RIPE NWORK-MNT