Olven-NET

BGP inherited
Cluster stats
Netblocks6 · 370 IPv4 addresses
Cluster ID204665368
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
46.46.137.0/27 Olven-NET RIPE ASSIGNED PA ● low
46.46.140.152/29 OLVEN-NET RIPE ASSIGNED PA ● low
46.46.153.208/28 Olven-NET RIPE ASSIGNED PA ● low
46.46.155.32/27 Olven-NET RIPE ASSIGNED PA ● low
46.46.155.64/27 Olven-NET RIPE ASSIGNED PA ● low
46.46.156.0/24 Olven-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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 (6 of 6)
Possible discrepancies (1)

These blocks are registered to Olven-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

46.46.156.0/24 /24 authorized for AS29470 — JSC "RetnNet"

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-RUBYCOM