OVP Software

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks4
IPv6 2 prefixes (largest 2a05:e9c0:6800::/40)
Record ID246684086
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
213.32.45.96/28 OVP Software RIPE ASSIGNED PA ● high
95.59.222.240/30 OVP_KAP RIPE ASSIGNED PA ● low
2a05:e9c0:6800::/40 OVP-CAI-DP RIPE ASSIGNED ● low
2a05:e9c0:7400::/40 OVP-SKP-DP RIPE ASSIGNED ● low

IPv6 ranges (2)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (4 of 4)
Possible discrepancies (2)

These blocks are registered to OVP Software 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.

2a05:e9c0:6800::/40 /40 authorized for AS62651 — Strong Technology, LLC.
2a05:e9c0:7400::/40 /40 authorized for AS62651 — Strong Technology, LLC.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT NETPROTECT-MNT ORG-OS146-RIPE OVH-MNT