HEISE-NET

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

Footprint over time

4 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-13

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
58.246.124.196/30 Heise APNIC ASSIGNED NON-PORTABLE ● low
82.98.94.32/30 HEISE-NET RIPE ASSIGNED PA ● low
82.98.94.40/29 HEISE-NET RIPE ASSIGNED PA ● low
212.19.61.8/29 HEISE-NET RIPE ASSIGNED PA ● low
213.83.4.112/28 HEISE-NET RIPE ASSIGNED PA ● low
2a00:e68:14::/48 HEISE RIPE ALLOCATED-BY-LIR ● low
2a02:2e0:3fe::/48 HEISE-NET RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “HEISE” — 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: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
Possible discrepancies (1)

These blocks are registered to HEISE-NET 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.

2a00:e68:14::/48 /48 authorized for AS15743 — net.de AG

NIC Handles

DUMY-RIPE DUMY-RIPE IPH-MNT MAINT-CNCGROUP-SH PLUSLINE-MNT YR194-AP YR194-AP