Data as of Nov 11, 2026

84.239.41.0/24

Anonymizer · VPN

Datacamp Limited · space held by INVITE Systems SRL

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

Path

1 · Holder
record created Apr 23, 2019
2 · Leased from
not leased
3 · Announced by
AS212238 Datacamp Limited
since Feb 2024 · 2.7 yr ago
4 · Use
VPN servicesnamed Kape Technologies
VPN

Operators, sellers and brokers

VPN services

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

Lineage

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

84.239.41.0/24

From the registry to its use

  1. Jun 20, 2013– Aug 1, 2013
    Announced
    AS199467 Hossein Zangooei
  2. Jul 4, 2017
    Reallocated
    INVITE Systems SRL
    SUB-ALLOCATED PA
    84.239.32.0/19
  3. Jul 29, 2017– Aug 23, 2019
    Announced
    AS44679 INVITE Systems SRL
    Hosting
  4. Apr 23, 2019
    Registry record
    INVITE Systems SRL
    ALLOCATED PA
    84.239.0.0/18
  5. Nov 28, 2019– Mar 23, 2023
    Announced
    AS44679 INVITE Systems SRL
    Hosting
  6. Jun 28, 2023– Feb 22, 2024
    Announced
    AS174 Cogent Communications, LLC
    Internet provider
  7. Feb 23, 2024– today
    Announced
    AS212238 Datacamp Limited
    Hosting
  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
84.239.0.0/1816,384RO-AD-NET-20110804INVITE Systems SRL (ORG-ANMM3-RIPE) · ROALLOCATED PAApr 23, 2019abuse@invitesys.ro
└ 84.239.32.0/198,192INVITE-SYSTEMSINVITE Systems SRL (ORG-ANMM3-RIPE) · ROSUB-ALLOCATED PAJul 4, 2017abuse@invitesys.ro
└ 84.239.41.0/25128BINBOX-ConcordunknownSUB-ALLOCATED PAApr 25, 2023abuse@invitesys.ro
via INVITE-SYSTEMS
└ 84.239.41.128/25128BINBOX-PhiladelphiaunknownSUB-ALLOCATED PAApr 25, 2023abuse@invitesys.ro
via INVITE-SYSTEMS

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
Jun 2013
Current origin since
Feb 2024 · 2.7 yr
Origin networks
4
Last change of origin
Feb 2024
Recorded history

History

Handoffs
3