Data as of Nov 18, 2026

85.234.56.0/24

17 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Always-on exits
3
18% of its exits
Providers
49
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

4.2K observations

Proxy providers listing exits

  • AETHYN_BASIC
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • LemonPrime
  • LightningProxies
  • MagneticProxy
  • MangoProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.234.32.0/198,192RU-MTU-20050428MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAApr 28, 2005abuse@mtu.ru
└ 85.234.48.0/204,096PTCOMMNETMTS PenzaASSIGNED PAJan 3, 2007abuse@mtu.ru
via RU-MTU-20050428

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 85.234.32.0/19

85.234.32.0/19

Routing history

Pattern
Stable
First seen
Dec 2005
Current origin since
Dec 2005 · 21 yr
Origin networks
1