Data as of Nov 17, 2026

85.31.116.0/22

18 residential-proxy exits · 30 days

OOO Telecom TZ

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
18
1.8% of its addresses · 30 days
Always-on exits
1
5.6% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
61
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HydraProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
85.31.116.0/24
since Feb 2025
AS15672Residential18
1 always on
OOO Telecom TZ
85.31.117.0/24
since Feb 2025
AS15672ResidentialOOO Telecom TZ
85.31.118.0/24
since Feb 2025
AS15672ResidentialOOO Telecom TZ
85.31.119.0/24
since Feb 2025
AS15672ResidentialOOO 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.116.0/24256TELECOM-TZ-NETNet for ip single static assignment clients MoscowASSIGNED PAMar 25, 2026abuse@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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2005
Current origin since
Nov 2014 · 12 yr
Origin networks
2
Last change of origin
Nov 2014
Recorded history

History

Handoffs
1