TNSE-CUST-LIDL-SVERIGE

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

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
213.115.1.168/29 TNSE-CUST-LIDL-SVERIGE RIPE ASSIGNED PA ● low
213.115.8.88/29 TNSE-CUST-LIDL-SVERIGE RIPE ASSIGNED PA ● low
213.115.20.128/29 TNSE-CUST-LIDL-SVERIGE-AB RIPE ASSIGNED PA ● low
213.115.28.96/29 TNSE-CUST-Lidl-Sverige-AB RIPE ASSIGNED PA ● low
213.115.35.192/29 TNSE-CUST-LIDL-SVERIGE RIPE ASSIGNED PA ● low
213.115.38.248/29 TNSE-CUST-LIDL-SVERIGE RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE TNSE-MNT