JMP Technology Services GmbH

DE-JMP-NET6-7
BGP inherited
Cluster stats
Netblocks7
All fragments 9 blocks across 3 clusters
Cluster ID211690527
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a0a:d6c0:7::/48 DE-JMP-NET6-7 RIPE ASSIGNED ● low
2a0a:d6c0:5000::/48 DE-JMP-NET6-7 RIPE ASSIGNED ● low
2a0a:d6c0:5001::/48 DE-JMP-NET6-7 RIPE ASSIGNED ● low
2a0a:d6c0:5002::/48 DE-JMP-NET6-7 RIPE ASSIGNED ● low
2a0a:d6c0:5003::/48 DE-JMP-NET6-7 RIPE ASSIGNED ● low
2a0a:d6c0:5004::/48 DE-JMP-NET6-7 RIPE ASSIGNED ● low
2a0a:d6c0:5006::/48 DE-JMP-NET6-7 RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “DE JMP NET6” — 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: F how networks compare →
14.3% of checked blocks have valid RPKI ROA coverage (1 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ch-jmptechnology-1-mnt