Lite Solutions

BGP inherited
Cluster stats
Netblocks13
All fragments 15 blocks across 2 clusters
Cluster ID205056354
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

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

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.196.128.248/30 Lite Solutions RIPE ASSIGNED PA ● high
51.77.90.184/29 Lite Solutions RIPE LEGACY ● high
51.178.161.40/30 Lite Solutions RIPE LEGACY ● high
51.178.161.44/30 Lite Solutions RIPE LEGACY ● high
51.178.161.48/30 Lite Solutions RIPE LEGACY ● high
51.254.59.48/29 Lite Solutions RIPE LEGACY ● high
54.38.7.32/28 Lite Solutions RIPE LEGACY ● high
162.19.140.48/29 Lite Solutions RIPE LEGACY ● high
176.31.192.12/30 Lite Solutions RIPE ASSIGNED PA ● high
178.33.89.36/30 Lite Solutions RIPE ASSIGNED PA ● high
193.70.22.88/29 Lite Solutions RIPE ASSIGNED PA ● high
193.70.23.128/29 Lite Solutions RIPE ASSIGNED PA ● high
193.70.23.136/29 Lite Solutions RIPE ASSIGNED PA ● high

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE ORG-LS295-RIPE OVH-MNT