Data as of Nov 20, 2026

45.92.230.0/24

Anonymizer · VPN

Datacamp Limited · space held by Panq B.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
VPN
Risk
75 / 100 · High
Recently moved
Recent change
New origin May 2026
from AS206150 F.N.S. Holdings Limited, after 5.4 years unannounced
IPv4 market

Path

Announced by AS212238 since May 2026 · 6 mo ago
1 · Holder
record created Dec 27, 2021
2 · Leased from
3 · Announced by
AS212238 Datacamp Limited
since May 2026 · 6 mo ago
4 · Use
VPN servicesnamed Kape Technologies
VPN

Operators, sellers and brokers

VPN services

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

Lineage

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

45.92.230.0/24

From the registry to its use

  1. Jul 19, 2019– Jul 30, 2019
    Announced
    AS206164 F.N.S. Holdings Limited
    Hosting
  2. Oct 17, 2020– Dec 27, 2020
    Announced
    AS206150 F.N.S. Holdings Limited
    Hosting
  3. Dec 27, 2021
    Registry record
    Panq B.V.
    ALLOCATED PA
    45.92.228.0/22
  4. May 29, 2026
    Assigned
    VPN Consumer San Francisco, United States of America
    ASSIGNED PA
    45.92.230.0/24
  5. May 29, 2026
    Route object
    AS212238 Datacamp Limited
    RIPE route object for AS212238 Datacamp Limited, maintainer PREFIXBROKER-MNT
  6. May 31, 2026– today
    Announced
    AS212238 Datacamp Limited
    Hosting
  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.92.228.0/221,024NL-PANQ-20190702Panq B.V. (ORG-WBB1-RIPE) · NLALLOCATED PADec 27, 2021abuse@panq.nl
└ 45.92.230.0/24256SAN-FRANCISCO-CA-USA-45-92-230-0VPN Consumer San Francisco, United States of America (ORG-VCSF1-RIPE) · USASSIGNED PAMay 29, 2026abuse-reports@vpnconsumer.com

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
Jul 2019
Current origin since
May 2026 · 6 mo
Origin networks
3
Last change of origin
May 2026
Recorded history

History

Handoffs
2