Data as of Nov 16, 2026

66.56.82.0/24

Anonymizer · VPN30 residential-proxy exits · 30 days

Datacamp Limited · space held by Nimbus IP Networks BV

Announcement
this exact prefix
RPKI valid
Announced by
Type
VPN

Residential-proxy exits

Proxy exits
30
12% of its addresses · 30 days
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

18K observations
IPv4 market

Path

1 · Holder
record created Mar 18, 2025
2 · Leased from
3 · Announced by
AS212238 Datacamp Limited
since Jun 2025 · 17 mo ago
4 · Use
VPN servicesnamed Kape Technologies, CyberGhost
VPN

Operators, sellers and brokers

VPN services

NameParentIn 66.56.82.0/24/24s
Kape Technologies
22688%
1
CyberGhostKape Technologies
3012%
1

Lineage

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

66.56.82.0/24

From the registry to its use

  1. Sep 15, 2010– Dec 1, 2010
    Announced
    AS26642 AnchorFree Inc.
  2. Jul 1, 2020– Jan 11, 2025
    Announced
    AS203999 Geekyworks IT Solutions Pvt Ltd
  3. Mar 18, 2025
    Registry record
    Nimbus IP Networks BV
    ALLOCATED PA
    66.56.80.0/20
  4. Mar 19, 2025
    Assigned
    VPN Consumer Toronto, Canada
    ASSIGNED PA
    66.56.82.0/24
  5. Mar 19, 2025
    Route object
    AS212238 Datacamp Limited
    RIPE route object for AS212238 Datacamp Limited, maintainer PREFIXBROKER-MNT
  6. Jun 17, 2025– today
    Announced
    AS212238 Datacamp Limited
    Hosting
  7. today
    Leased from
    PrefixBroker
    IP broker
  8. today
    Used
    Kape Technologies
    VPN
  9. today
    Used
    CyberGhost
    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
66.56.80.0/204,096NL-NIMBUS-20081209Nimbus IP Networks BV (ORG-NINB1-RIPE) · NLALLOCATED PAMar 18, 2025abuse@nimbusip.nl
└ 66.56.82.0/24256TORONTO-ON-CA-66-56-82-0VPN Consumer Toronto, Canada (ORG-VCTC1-RIPE) · CAASSIGNED PAMar 19, 2025abuse-reports@vpnconsumer.com

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Sep 2010
Current origin since
Jun 2025 · 1.4 yr
Origin networks
3
Last change of origin
Jun 2025
Recorded history

History

Handoffs
2