LZB

BGP inherited
Cluster stats
Netblocks9 · 268 IPv4 addresses
Registered in Netherlands (8) · Germany (1)
All fragments 11 blocks across 3 clusters
Cluster ID208842824
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

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.112.246.253/32 LZB RIPE ASSIGNED PA ● low
80.112.247.95/32 LZB RIPE ASSIGNED PA ● low
80.112.247.199/32 LZB RIPE ASSIGNED PA ● low
80.112.247.209/32 LZB RIPE ASSIGNED PA ● low
83.167.198.216/30 LZB RIPE ASSIGNED PA ● low
159.100.84.61/32 LZB RIPE LEGACY ● low
159.100.91.112/29 LZB RIPE LEGACY ● low
194.174.205.0/24 LZB RIPE ASSIGNED PA ● low
212.78.222.104/30 LZB RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “LZB” — 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.

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.9% of checked blocks have valid RPKI ROA coverage (8 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE TNF-MNT UUNETDE-I