Data as of Nov 19, 2026

134.17.94.0/24

6 residential-proxy exits · 30 days

Mobile TeleSystems JLLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
41
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

643 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
134.17.88.0/21
since May 2012
AS25106Mobile7Mobile TeleSystems JLLC

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
134.17.0.0/1665,536BY-MTS-20111103Mobile TeleSystems JLLC (ORG-MTJ1-RIPE) · BYALLOCATED PANov 3, 2011abuse@mts.by
└ 134.17.88.0/212,048MTSBYMobile TeleSystems JLLCASSIGNED PAApr 20, 2012abuse@mts.by
via BY-MTS-20111103

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
Reactivated
First seen
Dec 2008
Current origin since
May 2026 · 6 mo
Origin networks
2
Last change of origin
May 2026
Recorded history

History

Handoffs
1