Data as of Nov 18, 2026

134.17.16.0/24

3 residential-proxy exits · 30 days

Mobile TeleSystems JLLC

Announcement
this exact prefix
RPKI invalid (length)
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
31
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

1.8K observations

Proxy providers listing exits

  • 9HTTP
  • 9Proxy
  • BestProxy
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EZProxies
  • GSocks
  • Geonix
  • Geonode
  • HideProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • NSocks
  • NextProxy
  • Oxylabs
  • ProxiesVision
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • TrueProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
134.17.16.0/21
since Oct 2019
AS25106Mobile14
1 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.16.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

First seen
Before our records
Origin networks
1