Data as of Nov 22, 2026

176.241.102.0/24

37 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
37
14% of its addresses · 30 days
Providers
42
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

597 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • IPFly
  • Infatica
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • ResiProxies
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
176.241.96.0/212,048RU-MTU-20111206MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 6, 2011abuse@mtu.ru
└ 176.241.102.0/24256LANCK-USERPJSC MTSASSIGNED PAJun 9, 2012abuse@mtu.ru
via RU-MTU-20111206

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

176.241.96.0/21

Routing history

Pattern
Stable
First seen
Dec 2011
Current origin since
Dec 2012 · 14 yr
Origin networks
2
Last change of origin
Dec 2012
Recorded history

History

Handoffs
1