Data as of Nov 16, 2026

95.139.63.0/24

39 residential-proxy exits · 30 days

MTS PJSC

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address
Recent change
New origin Sep 2026
its first announcement on record

Residential-proxy exits

Proxy exits
39
15% of its addresses · 30 days
Providers
37
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.8K observations

Proxy providers listing exits

  • 9Proxy
  • AnyIP
  • BestProxy
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • Geonode
  • GhostConnect
  • HPROXY
  • HideProxy
  • IP2WORLD
  • IPFly
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • PYPROXY
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.139.0.0/17
since Feb 2023
AS8359Mobile3,765
502 always on
MTS PJSC

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.139.0.0/1732,768RU-MTU-20090325MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMar 25, 2009abuse@mtu.ru
└ 95.139.56.0/212,048MTS-FBN-IvanovounknownASSIGNED PASep 11, 2026abuse@mtu.ru
via RU-MTU-20090325

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

95.139.56.0/21

Routing history

Pattern
Stable
First seen
Sep 2026
Current origin since
Sep 2026 · 2 mo
Origin networks
1