DATACLUB-LV

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8 · 1,280 IPv4 addresses
IPv6 3 prefixes (largest 2a02:4840:1::/48)
Cluster ID215345414
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · 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
84.38.130.0/24 DATACLUB-LV RIPE ASSIGNED PA ● low
84.38.131.0/24 DATACLUB-LV RIPE ASSIGNED PA ● low
84.38.132.0/24 DATACLUB-LV RIPE ASSIGNED PA ● low
84.38.134.0/24 DATACLUB-LV RIPE ASSIGNED PA ● low
84.38.135.0/24 DATACLUB-LV RIPE ASSIGNED PA ● low
2a02:4840::/48 DATACLUB-LV RIPE ASSIGNED ● low
2a02:4840:1::/48 DATACLUB-LV RIPE ASSIGNED ● low
2a02:4840:2::/48 DATACLUB-LV RIPE ASSIGNED ● low

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
RPKI-inferred operator SIA RixHost
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

DATACLUB-MNT DUMY-RIPE DUMY-RIPE