Data as of Nov 14, 2026

92.246.176.0/20

20 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
20
0.49% of its addresses · 30 days
Always-on exits
2
10% of its exits
Spread
11 of 16
/24s with at least one exit
Providers
48
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

3.3K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • IPRoyal
  • InfiniteProxies
  • KindProxy
  • Kookey
  • NSocks
  • NextProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • SwiftProxy
  • TalorData
  • Thordata
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
92.246.160.0 - 92.246.223.25516,384RU-MTU-20080422MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 29, 2016abuse@mtu.ru
└ 92.246.176.0/204,096PTCOMMNETMTS PenzaASSIGNED PADec 8, 2008abuse@mtu.ru
via RU-MTU-20080422

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

92.246.160.0/19

Routing history

Pattern
Stable
First seen
May 2008
Current origin since
May 2008 · 18 yr
Origin networks
1