LBX

BGP inherited
Cluster stats
Netblocks10
All fragments 13 blocks across 4 clusters
Cluster ID210260329
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
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
46.129.133.192/30 LBX RIPE ASSIGNED PA ● low
46.129.152.224/30 LBX RIPE ASSIGNED PA ● low
85.146.200.232/30 LBX RIPE ASSIGNED PA ● low
85.146.201.124/30 LBX RIPE ASSIGNED PA ● low
93.117.202.176/30 LBX RIPE ASSIGNED PA ● low
93.117.228.13/32 LBX RIPE ASSIGNED PA ● low
93.117.228.208/29 LBX RIPE ASSIGNED PA ● low
93.117.239.48/30 LBX RIPE ASSIGNED PA ● low
159.100.74.160/28 LBX RIPE LEGACY ● low
159.100.95.236/30 LBX RIPE LEGACY ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “LBX” — 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: 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 TNF-MNT ZIGGO-AUTOREG1