Data as of Nov 20, 2026

134.17.14.0/24

18 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
18
7.0% of its addresses · 30 days
Always-on exits
2
11% of its exits
Providers
65
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

5.9K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • BUYPERSONALPROXY
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FROXY
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HPROXY
  • HideProxy
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
134.17.0.0/20
since Feb 2012
AS25106Mobile75
11 always on
Mobile 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.0.0/204,096MTSBYMobile TeleSystems JLLCASSIGNED PAFeb 7, 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