Data as of Nov 13, 2026

85.196.233.0/24

3 residential-proxy exits · 30 days

AS STV

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin Oct 10, 2026
from AS61307 AS STV, after 6.2 years unannounced

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
2
67% of its exits
Providers
33
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

6.8K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.196.192.0/18
since Dec 2012
AS61307Residential330
45 always on
AS STV

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.196.192.0/1816,384EE-STV-20050117AS STV (ORG-AS47-RIPE) · EEALLOCATED PAJan 17, 2005abuse@stv.ee
└ 85.196.232.0/23512STV_NETWORKParnu LAN 110ASSIGNED PAMay 6, 2013abuse@stv.ee
via EE-STV-20050117

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

Covering aggregate above, the prefix's own history below

85.196.224.0/19

Routing history

Pattern
Stable
First seen
Oct 2019
Current origin since
Oct 10, 2026 · 1 mo
Origin networks
1