Data as of Nov 21, 2026

213.59.129.0/24

9 residential-proxy exits · 30 days

OOO SET · space held by MTS PJSC

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
42
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

3.0K observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • IPFly
  • IPOasis
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • 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
213.59.128.0/198,192RU-MTU-20000224MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 30, 2025abuse@mtu.ru
└ 213.59.128.0/221,024ZT-UFA-NETZelenaya Ufa NetworkASSIGNED PAJan 22, 2015abuse@mtu.ru
via RU-MTU-20000224

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 213.59.128.0/22

213.59.128.0/22

Routing history

Pattern
Stable
First seen
Mar 2015
Current origin since
Mar 2015 · 12 yr
Origin networks
1