Data as of Nov 12, 2026

185.35.96.0/22

2 residential-proxy exits · 30 days

Weserve B.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
96% of it

Residential-proxy exits

Proxy exits
2
0.20% of its addresses · 30 days
Always-on exits
1
50% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
23
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

4.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.35.99.0/2411
185.35.98.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • CliProxy
  • DataImpulse
  • Evomi
  • FlashProxy
  • FloppyData
  • GeekProxy
  • Geonode
  • GloryCloud
  • InfiniteProxies
  • Kookey
  • Novada
  • PSBProxy
  • Proxy4U
  • ProxyWing
  • SwiftProxy
  • Thordata

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
185.35.96.0/221,024NL-WESERVE-20130916Weserve B.V. (ORG-WB37-RIPE) · NLALLOCATED PADec 17, 2018abuse@weserve.nl
└ 185.35.96.0/23512NL-WESERVE-20210311Weserve NLASSIGNED PAMay 11, 2015abuse@weserve.nl
via NL-WESERVE-20130916
└ 185.35.99.192/2816NLISPKIRPESTEINHandelsonderneming Kirpestein B.V.ASSIGNED PAJun 22, 2021abuse@weserve.nl
via NL-WESERVE-20130916
└ 185.35.99.208/2816NLISPKIRPESTEINHandelsonderneming Kirpestein B.V.ASSIGNED PAJun 22, 2021abuse@weserve.nl
via NL-WESERVE-20130916
└ 185.35.99.224/298NLISPKIRPESTEINHandelsonderneming Kirpestein B.V.ASSIGNED PAJun 22, 2021abuse@weserve.nl
via NL-WESERVE-20130916

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

1,024 addresses
TypeAddressesShareRanges
Residential98496%2
Business403.9%3

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Mar 2015
Current origin since
Jan 2024 · 2.9 yr
Origin networks
3
Last change of origin
Jan 2024
Recorded history

History

Handoffs
2