Data as of Nov 20, 2026

109.174.60.0/24

8 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
3
38% of its exits
Providers
55
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

6.7K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • YumiProxy

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.0.0/1816,384HOMENETWHITEJSC Sibel TelecomASSIGNED PADec 3, 2009abuse@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