Data as of Nov 16, 2026

134.17.28.0/24

12 residential-proxy exits · 30 days

Mobile TeleSystems JLLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
24
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

96 observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • GloryCloud
  • IPFly
  • IPPeak
  • KindProxy
  • Maskify
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • Novada
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RapidProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
134.17.24.0/21
since Mar 2013
AS25106Mobile44
3 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

Pattern
Stable
First seen
Oct 2020
Current origin since
Oct 2020 · 6.1 yr
Origin networks
1