Lim Ops

LimOps
Registry
Cluster stats
Netblocks7
All fragments 12 blocks across 2 clusters
Cluster ID211813761
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 3 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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a07:1bc0::/48 LimOps RIPE AGGREGATED-BY-LIR ● low
2a07:1bc0:1::/48 LimOps RIPE AGGREGATED-BY-LIR ● low
2a07:1bc0:2::/48 LimOps RIPE AGGREGATED-BY-LIR ● low
2a07:1bc0:3::/48 LimOps RIPE AGGREGATED-BY-LIR ● low
2a07:1bc0:4::/48 LimOps RIPE AGGREGATED-BY-LIR ● low
2a07:1bc0:5::/48 LimOps RIPE AGGREGATED-BY-LIR ● low
2a07:1bc0:6::/48 LimOps RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE LIMOPS-MNT