Data as of Nov 21, 2026

31.29.212.0/24

4 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
35
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • GSocks
  • GeekProxy
  • IPFly
  • Infatica
  • MagneticProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • VProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.29.212.0/23
since Oct 2025
AS48612Residential5
2 always on
MTS PJSC

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
31.29.128.0/1732,768RU-MTU-20110309MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMar 9, 2011abuse@mtu.ru
└ 31.29.212.0/221,024CMST-ORENBURG-20130115Orenburg TsuS of Privolzhsky branch of CJS Komstar-RegionyASSIGNED PAAug 22, 2017abuse@mtu.ru
via RU-MTU-20110309

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2013
Current origin since
Jan 2013 · 14 yr
Origin networks
1