LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

85.140.56.0/24

2 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
31
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

21 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Shifter
  • StrikeProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.140.0.0/15
since May 2005
AS8359Residential3,197
75 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.56.0/221,024RU-MTS-KALUGA-1unknownASSIGNED PASep 22, 2017abuse@mtu.ru
via RU-MTU-20041213

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2019
Current origin since
May 2019 · 7.5 yr
Origin networks
1