Lu Lu Lemon

LuLuLemon
Registry
Cluster stats
Netblocks10
All fragments 24 blocks across 8 clusters
Cluster ID210595603
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
85.184.192.93 – 85.184.192.94 LuLuLemon RIPE ASSIGNED PA ● low
85.184.192.129 – 85.184.192.130 LuLuLemon RIPE ASSIGNED PA ● low
85.184.192.241 – 85.184.192.246 LuLuLemon RIPE ASSIGNED PA ● low
85.184.193.209 – 85.184.193.210 LuLuLemon RIPE ASSIGNED PA ● low
85.184.193.241 – 85.184.193.246 LuLuLemon RIPE ASSIGNED PA ● low
85.184.194.121 – 85.184.194.126 LuLuLemon RIPE ASSIGNED PA ● low
85.184.194.164/32 LuLuLemon RIPE ASSIGNED PA ● low
85.184.199.18/32 LuLuLemon RIPE ASSIGNED PA ● low
85.184.199.143/32 LuLuLemon RIPE ASSIGNED PA ● low
195.89.150.136/30 LULULEMON RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “LuLuLemon” — 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 →
10.0% of checked blocks have valid RPKI ROA coverage (1 of 10)
No discrepancies found among checked blocks.

NIC Handles

DK88908-MNT DUMY-RIPE DUMY-RIPE VODAFONE-WORLDWIDE-MNTNER