Data as of Nov 14, 2026

98.159.233.0/24

Anonymizer · VPN

Datacamp Limited · space held by LogicWeb Inc.

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

Path

1 · Holder
record created Mar 26, 2010
2 · Leased from
3 · Announced by
AS212238 Datacamp Limited
since Feb 2025 · 21 mo ago
4 · Use
VPN servicesnamed Kape Technologies
VPN

Operators, sellers and brokers

VPN services

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

Lineage

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

98.159.233.0/24

From the registry to its use

  1. Mar 26, 2010
    Registry record
    LogicWeb Inc.
    Direct Allocation
    98.159.224.0/20
  2. Dec 1, 2013– May 1, 2016
    Announced
    AS12025 Iron Mountain Data Center
    Hosting
  3. Jun 22, 2016– Mar 20, 2019
    Announced
    AS15003 Leaseweb USA, Inc.
  4. Apr 14, 2019– May 19, 2019
    Announced
    AS46562 Performive LLC
    Hosting
  5. May 2, 2020– Dec 5, 2022
    Announced
    AS36351 IBM Cloud
    Hosting
  6. Feb 16, 2022
    Route object
    AS36351 IBM Cloud
    ARIN route object for AS36351 IBM Cloud, maintainer MNT-LOGIC-25
  7. Feb 17, 2025– today
    Announced
    AS212238 Datacamp Limited
    Hosting
  8. Feb 27, 2025
    Route object
    AS212238 Datacamp Limited
    ARIN route object for AS212238 Datacamp Limited, maintainer MNT-LOGIC-25
  9. Mar 14, 2025
    Assigned
    VPN Consumer Network
    Reassigned
    98.159.233.0/24
  10. today
    Leased from
    LogicWeb
    IP broker
  11. 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
98.159.224.0/204,096LOGICWEBLogicWeb Inc. (LOGIC-25) · USDirect AllocationMar 26, 2010abuse@logicweb.com
└ 98.159.233.0/24256VPN-CONSUMER-NETWORKVPN Consumer Network (C11133578) · USReassignedMar 14, 2025abuse@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
Reactivated
First seen
Dec 2013
Current origin since
Feb 2025 · 1.7 yr
Origin networks
5
Last change of origin
Feb 2025
Recorded history

History

Handoffs
4