Data as of Nov 14, 2026

89.31.34.0/24

6 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
38
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Q2IP
  • RainProxy
  • RolaProxy
  • Shifter
  • StrikeProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.31.32.0/212,048RU-MTU-20100604MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJun 4, 2010abuse@mtu.ru
└ 89.31.32.0/221,024MTS-KURGANunknownASSIGNED PANov 29, 2017abuse@mtu.ru
via RU-MTU-20100604

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 89.31.32.0/21

89.31.32.0/21

Routing history

Pattern
Stable
First seen
Sep 2006
Current origin since
Jun 2010 · 16 yr
Origin networks
2
Last change of origin
Jun 2010
Recorded history

History

Handoffs
1