Schleupen SE

GLEIF verified
LEI
391200786Z4XRC4UWC39
Registered name
Schleupen SE
Jurisdiction
DE
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks6 · 1,099 IPv4 addresses
All fragments 12 blocks across 3 clusters
Cluster ID209104365
RegistryRIPE
Owner jurisdictionDE
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 391200786Z4XRC4UWC39
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.16.66.56/29 Schleupen SE RIPE ASSIGNED PA ● high
81.26.171.0/27 Schleupen SE RIPE ASSIGNED PA ● high
213.144.8.32/27 Schleupen SE RIPE ASSIGNED PA ● high
213.144.13.192/29 Schleupen SE RIPE ASSIGNED PA ● high
185.28.228.0/22 Schleupen SE RIPE ALLOCATED PA ● low
2a00:96e0::/32 Schleupen SE RIPE ALLOCATED-BY-RIR ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE LIR-SSE-IPMGMT-MNT ORG-SA1302-RIPE ORG-SA4290-RIPE RIPE-NCC-HM-MNT TXX-MNT