LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

91.239.157.0/24

8 anonymizer addresses · 3.1% · VPN9 residential-proxy exits · 30 days

Clouvider Limited

Announcement
this exact prefix
No RPKI
Announced by
AS62240
Type
Hosting
97% of it

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

8.1K observations
  • VPN · anonymizer
  • Hosting
IPv4 market

Path

1 · Holder
Clouvider Limited
record created Dec 14, 2022
2 · Leased from
not leased
3 · Announced by
AS62240 Clouvider Limited
since Nov 2020 · 6.0 yr ago
4 · Use
VPN servicesnamed Surfshark
Hosting

Operators, sellers and brokers

VPN services

NameParentIn 91.239.157.0/24/24s
SurfsharkNord Security
83.1%
1

Lineage

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

91.239.157.0/24

From the registry to its use

  1. Jun 1, 2012– Oct 8, 2014
    Announced
    AS24958 Cyberfort Limited
    Hosting
  2. Nov 17, 2019
    Route object
    AS62240 Clouvider Limited
    RIPE route object for AS62240 Clouvider Limited, maintainer CLOUVIDER-MNT
  3. Nov 10, 2020– today
    Announced
    AS62240 Clouvider Limited
    Hosting
  4. Dec 14, 2022
    Registry record
    Clouvider Limited
    ALLOCATED PA
    91.239.157.0/24
  5. today
    Used
    Surfshark
    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
91.239.157.0/24256UK-CLOUVIDER-20191112Clouvider Limited (ORG-CL248-RIPE) · GBALLOCATED PADec 14, 2022abuse@clouvider.net
└ 91.239.157.0/2816CLOUVIDER-HB-CLIENT-3935Customer allocation HB Client 3935ASSIGNED PANov 28, 2021abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.36/304CLOUVIDER-HB-CLIENT-4265Customer allocation HB Client 4265ASSIGNED PAApr 11, 2023abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.42/321CLOUVIDER-HB-CLIENT-272Customer allocation HB Client 272ASSIGNED PAJun 15, 2022abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.43/321CLOUVIDER-HB-CLIENT-272Customer allocation HB Client 272ASSIGNED PAJul 21, 2022abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.50/321CLOUVIDER-HB-CLIENT-14184Customer allocation HB Client 14184ASSIGNED PAMay 8, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.68/312CLOUVIDER-HB-CLIENT-5977Customer allocation HB Client 5977ASSIGNED PASep 23, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.82/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PADec 23, 2024abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.83/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PADec 23, 2024abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.84/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 7, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.85/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 7, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.86/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 7, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.90/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 9, 2024abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.91/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 9, 2024abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.92/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 9, 2024abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.93/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 9, 2024abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.94/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAApr 2, 2024abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.104/298CLOUVIDER-HB-CLIENT-2353Customer allocation HB Client 2353ASSIGNED PANov 28, 2021abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.112/2816PACKETHUB-20190723Packethub S.A. (ORG-PS433-RIPE)ASSIGNED PAFeb 23, 2023abuse@packethub.tech
└ 91.239.157.184/298CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAMar 29, 2023abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.210/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJun 19, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.211/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJun 19, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.212/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJun 19, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.213/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJun 19, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.214/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 15, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.216/298CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAMar 7, 2022abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.224/298CLOUVIDER-HB-CLIENT-157Customer allocation HB Client 157ASSIGNED PAApr 3, 2025abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.242/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 15, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.243/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 15, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.244/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 15, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.245/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 15, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.246/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 15, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.250/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 15, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.251/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 27, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.252/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAJan 29, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.253/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 5, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112
└ 91.239.157.254/321CLOUVIDER-HB-CLIENT-2916Customer allocation HB Client 2916ASSIGNED PAFeb 18, 2026abuse@clouvider.net
via UK-CLOUVIDER-20191112

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Hosting24897%3
VPNanonymizer83.1%8

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2012
Current origin since
Nov 2020 · 6.0 yr
Origin networks
2
Last change of origin
Nov 2020
Recorded history

History

Handoffs
1