Data as of Nov 22, 2026

109.110.59.0/24

7 residential-proxy exits · 30 days

Natalia Sergeevna Filicheva

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
38
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

12K observations

Proxy providers listing exits

  • 2Captcha
  • 9HTTP
  • AETHYN_ELITE
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • Infatica
  • LUMIPROXY
  • LemonPrime
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
109.110.32.0/198,192RU-PODRYAD-20091117Natalia Sergeevna Filicheva (ORG-NSF3-RIPE) · RUALLOCATED PAJun 19, 2019abuse@podryad.tv
└ 109.110.56.0/221,024PODRYAD-DYN-VPN-2Podryad - Customer Pool - 3ASSIGNED PAOct 23, 2010abuse@podryad.tv
via RU-PODRYAD-20091117

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

Who has announced 109.110.32.0/19

109.110.32.0/19

Routing history

Pattern
Stable
First seen
Aug 2011
Current origin since
Aug 2011 · 15 yr
Origin networks
1