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

85.141.112.0/21

2 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
2
0.10% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
24
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

70 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.141.112.0/2401
85.141.113.0/2401

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • BirdProxies
  • BottingTools
  • Byteful
  • CROXY
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • InfiniteProxies
  • NSocks
  • NodeMaven
  • Novada
  • PrivateProxy
  • Proxies.fo
  • ProxyEmpire
  • ProxyWing
  • RainProxy
  • Shifter
  • Thordata
  • VibeProxies
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.140.0.0/15
since May 2005
AS8359Residential3,193
71 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.141.112.0/212,048NovosibirskStaticIPNovosibirskASSIGNED PAAug 15, 2023abuse@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
Oct 2023
Current origin since
Oct 2023 · 3.1 yr
Origin networks
1