Data as of Nov 17, 2026

85.140.61.0/24

3 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • NovaProxy
  • Proxy-Seller
  • Proxy4U
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.140.60.0/22
since Feb 2021
AS41209Residential7
2 always on
MTS PJSC
85.140.0.0/15
since May 2005
AS8359Residential3,193
78 always on
MTS PJSC

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
85.140.0.0/15131,072RU-MTU-20041213MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 13, 2004abuse@mtu.ru
└ 85.140.60.0/23512RU-MTU-SAMARA-1MTS PJSC (ORG-ZM1-RIPE) · RUASSIGNED PAJan 23, 2020abuse@mtu.ru

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2021
Current origin since
Feb 2021 · 5.8 yr
Origin networks
1