Data as of Nov 12, 2026

45.8.17.0/24

Anonymizer · VPN150 residential-proxy exits · 30 days

Clouvider Limited · space held by TnR Technologies B.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
VPN
Risk
75 / 100 · High

Residential-proxy exits

Proxy exits
150
59% of its addresses · 30 days
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.5K observations
IPv4 market

Path

1 · Holder
record created Apr 12, 2019
2 · Leased from
3 · Announced by
AS62240 Clouvider Limited
since Mar 2022 · 4.7 yr ago
4 · Use
VPN servicesnamed Kape Technologies
VPN

Operators, sellers and brokers

VPN services

NameParentIn 45.8.17.0/24/24s
Kape Technologies
256100%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

45.8.17.0/24

From the registry to its use

  1. Apr 12, 2019
    Registry record
    TnR Technologies B.V.
    ALLOCATED PA
    45.8.16.0/22
  2. Apr 14, 2019– Apr 25, 2019
    Announced
    AS206164 F.N.S. Holdings Limited
    Hosting
  3. Aug 24, 2019– Aug 17, 2020
    Announced
    AS206804 Realcloud OU
    Hosting
  4. Dec 16, 2020– Mar 4, 2022
    Announced
    AS60781 LeaseWeb Netherlands B.V.
    Hosting
  5. Mar 5, 2022– today
    Announced
    AS62240 Clouvider Limited
    Hosting
  6. Mar 7, 2022
    Route object
    AS62240 Clouvider Limited
    RIPE route object for AS62240 Clouvider Limited, maintainer PREFIXBROKER-MNT
  7. today
    Leased from
    PrefixBroker
    IP broker
  8. today
    Used
    Kape Technologies
    VPN

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
45.8.16.0/221,024NL-TNRTECHNOLOGIES-20190412TnR Technologies B.V. (ORG-TTB8-RIPE) · NLALLOCATED PAApr 12, 2019abuse-45-8-16-0-22@tnrtechnologies.nl
└ 45.8.17.0/24256VPN-Consumer-NetworkunknownASSIGNED PADec 7, 2020abuse-45-8-16-0-22@tnrtechnologies.nl
via NL-TNRTECHNOLOGIES-20190412

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Apr 2019
Current origin since
Mar 2022 · 4.7 yr
Origin networks
4
Last change of origin
Mar 2022
Recorded history

History

Handoffs
3