LEVISTRAUSS-NET

BGP inherited
Cluster stats
Netblocks10
All fragments 12 blocks across 3 clusters
Cluster ID208799830
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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
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
176.88.189.216/30 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
176.236.155.68/30 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
213.14.88.172/32 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
213.14.92.100/32 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
213.14.101.71/32 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
213.74.59.184/32 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
213.74.78.116/32 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
213.74.119.6/32 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
213.74.194.204/32 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low
213.74.215.92/30 LEVISTRAUSS-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “LEVISTRAUSS” — 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 (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-TELETEK MNT-TELLCOM SOL-NET TURK-NET-MNT