Data as of Nov 13, 2026

93.185.255.0/24

3 residential-proxy exits · 30 days

AS STV

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

2.0K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxying
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
93.185.240.0/20
since Dec 2012
AS61307Residential349
4 always on
AS STV

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
93.185.240.0/204,096EE-STV-20080612AS STV (ORG-AS47-RIPE) · EEALLOCATED PAJun 12, 2008abuse@stv.ee
└ 93.185.255.0/24256STV_NETWORKTartu LanASSIGNED PAMay 6, 2013abuse@stv.ee
via EE-STV-20080612

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

93.185.248.0/21

Routing history

Pattern
Stable
First seen
Oct 2019
Current origin since
Nov 2025 · 12 mo
Origin networks
1