Data as of Nov 14, 2026

85.31.113.0/24

6 residential-proxy exits · 30 days

OOO Telecom TZ

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
40
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

451 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • APROXY
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.31.112.0/22
since Jun 2011
AS15672Residential17OOO Telecom TZ

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.31.112.0/212,048RU-TZ-20110211OOO Telecom TZ (ORG-TT4-RIPE) · RUALLOCATED PAFeb 11, 2011abuse@tz.ru
└ 85.31.113.0/24256TELECOM-TZ-NETNet for ip single static assignment clients MskASSIGNED PAFeb 10, 2014abuse@tz.ru
via RU-TZ-20110211

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
Aug 2005
Current origin since
Feb 2025 · 1.8 yr
Origin networks
2
Last change of origin
Nov 2014
Recorded history

History

Handoffs
1