SK-LIDL-BA

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8
IPv6 1 prefix (largest 2a00:1298:801e::/48)
All fragments 36 blocks across 21 clusters
Cluster ID213374870
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.168.95.32/29 SK-LIDL-BA RIPE ASSIGNED PA ● low
85.248.21.56/29 SK-LIDL-BA RIPE ASSIGNED PA ● low
85.248.43.184/29 SK-LIDL-BA RIPE ASSIGNED PA ● low
195.168.39.224/30 SK-LIDL-BA RIPE ASSIGNED PA ● low
195.168.144.16/30 SK-LIDL-BA RIPE ASSIGNED PA ● low
195.168.193.48/29 SK-LIDL-BA RIPE ASSIGNED PA ● low
195.168.193.208/28 SK-LIDL-BA RIPE ASSIGNED PA ● low
2a00:1298:801e::/48 SK-LIDL-BA RIPE ASSIGNED ● low

IPv6 ranges (1)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
Possible discrepancies (1)

These blocks are registered to SK-LIDL-BA but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:1298:801e::/48 /48 authorized for AS5578 — SWAN, a.s.

NIC Handles

DUMY-RIPE DUMY-RIPE GTSSK-MNT SWAN-MNT