JENNY

Handle
Cluster stats
Netblocks8
Registered in South Africa (3) · ZM (1)
All fragments 225 blocks across 161 clusters
Cluster ID213182892
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name 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
196.60.8.247/32 JENNY PEERINGDB ASSIGNED ● high
196.60.9.249/32 JENNY PEERINGDB ASSIGNED ● high
196.60.94.20/32 JENNY PEERINGDB ASSIGNED ● high
196.60.97.45/32 JENNY PEERINGDB ASSIGNED ● high
2001:43f8:1f0::1:45/128 JENNY PEERINGDB ASSIGNED ● high
2001:43f8:6d0::247/128 JENNY PEERINGDB ASSIGNED ● high
2001:43f8:6d0::9:249/128 JENNY PEERINGDB ASSIGNED ● high
2001:43f8:1680::20/128 JENNY PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “JENNY” — 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.
Combined view of all 161 name-family clusters →
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

AS327750