Data as of Nov 20, 2026

109.174.96.0/21

4 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
4
0.20% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
24
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

2.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
109.174.103.0/2411
109.174.96.0/2402
109.174.99.0/2401

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Decodo
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_TURBO
  • IPFly
  • IPPeak
  • Kookey
  • LOKIPROXY
  • LudaxProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PuraRoute
  • Q2IP
  • YumiProxy
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
109.174.0.0/1732,768RU-MTU-20091203MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 3, 2009abuse@mtu.ru
└ 109.174.96.0/212,048CBNET4CBNet Project NetworkASSIGNED PANov 2, 2010abuse@mtu.ru
via RU-MTU-20091203

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.174.0.0/17

109.174.0.0/17

Routing history

Pattern
Stable
First seen
Mar 2012
Current origin since
Mar 2012 · 15 yr
Origin networks
1