Data as of Nov 20, 2026

109.110.52.0/24

4 residential-proxy exits · 30 days

Natalia Sergeevna Filicheva

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
41
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • Ake.net
  • BUYPERSONALPROXY
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

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.48.0/212,048PODRYAD-DYN-VPN-2Podryad - Customer Pool - 2ASSIGNED 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