Data as of Nov 14, 2026

173.239.218.0/24

Anonymizer · VPN46 residential-proxy exits · 30 days

Clouvider Limited · space held by LogicWeb Inc.

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

Residential-proxy exits

Proxy exits
46
18% of its addresses · 30 days
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.1K observations
IPv4 market

Path

1 · Holder
record created May 6, 2010
2 · Leased from
3 · Announced by
AS62240 Clouvider Limited
since Nov 2022 · 4.0 yr ago
4 · Use
VPN servicesnamed Kape Technologies
VPN

Operators, sellers and brokers

VPN services

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

Lineage

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

173.239.218.0/24

From the registry to its use

  1. May 6, 2010
    Registry record
    LogicWeb Inc.
    Direct Allocation
    173.239.192.0/18
  2. Dec 22, 2013– Aug 8, 2015
    Announced
    AS12025 Iron Mountain Data Center
    Hosting
  3. Jun 6, 2018– Apr 7, 2020
    Announced
    AS20473 The Constant Company, LLC
    Hosting
  4. Jun 7, 2020– Sep 10, 2020
    Announced
    AS61317 Hivelocity LLC
    Hosting
  5. Aug 30, 2020– Oct 6, 2022
    Announced
    AS207907 Elia Kessler
  6. Sep 23, 2020– Oct 4, 2020
    Announced
    AS3356 Level 3 Parent, LLC
    Internet provider
  7. Nov 8, 2022
    Route object
    LogicWeb
    RADB route object for AS62240 Clouvider Limited, maintainer MAINT-AS64286
  8. Nov 12, 2022– today
    Announced
    AS62240 Clouvider Limited
    Hosting
  9. today
    Leased from
    LogicWeb
    IP broker
  10. 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
173.239.192.0/1816,384LOGICWEBLogicWeb Inc. (LOGIC-25) · USDirect AllocationMay 6, 2010abuse@logicweb.com
└ 173.239.218.0/24256LOGICWEBunknownReassignedNov 20, 2024abuse@logicweb.com
via LOGICWEB

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
Dec 2013
Current origin since
Nov 2022 · 4.0 yr
Origin networks
6
Last change of origin
Nov 2022
Recorded history

History

Handoffs
5