Data as of Nov 19, 2026

31.186.148.0/22

8 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
8
0.78% of its addresses · 30 days
Always-on exits
3
38% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
34
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

4.5K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GeekProxy
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxying
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.186.128.0/19
since May 2011
AS21365Residential1,071
40 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.186.128.0/198,192RU-MTU-20110324MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMar 24, 2011abuse@mtu.ru
└ 31.186.144.0/212,048MTS-NET-BARN-V14BarnaulASSIGNED PASep 7, 2017abuse@mtu.ru
via RU-MTU-20110324

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
Aug 2025
Current origin since
Aug 2025 · 1.2 yr
Origin networks
1