LV-BEGET

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks11 · 4,864 IPv4 addresses
Record ID239247290
RegistryRIPE
Customerssee who runs inside 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

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.128.32.0/22 LV-BEGET RIPE ASSIGNED PA ● low
37.233.82.0/23 LV-BEGET RIPE ASSIGNED PA ● low
37.233.84.0/23 LV-BEGET RIPE ASSIGNED PA ● low
37.233.86.0/24 LV-BEGET RIPE ASSIGNED PA ● low
45.11.94.0/24 LV-BEGET RIPE ASSIGNED PA ● low
45.145.5.0/24 LV-BEGET RIPE ASSIGNED PA ● low
45.145.6.0/24 LV-BEGET RIPE ASSIGNED PA ● low
77.73.233.0/24 LV-BEGET RIPE ASSIGNED PA ● low
83.222.20.0/23 LV-BEGET RIPE ASSIGNED PA ● low
90.156.254.0/23 LV-BEGET RIPE ASSIGNED PA ● low
91.218.142.0/23 LV-BEGET RIPE ASSIGNED PA ● low

Footprint over time

11 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-09-06

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (11 of 11)
RPKI-inferred operator RETN Limited
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

BEGET-MNT DUMY-RIPE DUMY-RIPE