Data as of Nov 13, 2026

85.236.176.0/20

152 residential-proxy exits · 30 days

LLC SIP 'NIS'

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

Residential-proxy exits

Proxy exits
152
3.7% of its addresses · 30 days
Always-on exits
15
9.9% of its exits
Spread
16 of 16
/24s with at least one exit
Providers
103
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

39K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSALE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PYPROXY
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.236.160.0/198,192RU-TAHION-20050519LLC SIP "NIS" (ORG-LS21-RIPE) · RUALLOCATED PAMay 19, 2005abuse@samaralan.ru
└ 85.236.176.0/24256TAHION-ISP-NETTAHION ISP NetworkASSIGNED PAJul 3, 2009abuse@samaralan.ru
via RU-TAHION-20050519
└ 85.236.177.0/24256TAHION-ISP-NETTAHION ISP NetworkASSIGNED PAJul 3, 2009abuse@samaralan.ru
via RU-TAHION-20050519
└ 85.236.178.0/24256TAHION-ISP-NETLLC SIP "NIS" (ORG-LS21-RIPE) · RUASSIGNED PAAug 14, 2013abuse@samaralan.ru
└ 85.236.179.0/24256TAHION-ISP-NETTAHION ISP NetworkASSIGNED PASep 16, 2005abuse@samaralan.ru
via RU-TAHION-20050519
└ 85.236.180.0 - 85.236.187.2552,048TAHIONISP-BBSBroadband service IP poolsASSIGNED PAOct 19, 2009abuse@samaralan.ru
via RU-TAHION-20050519
└ 85.236.188.0/221,024TAHIONISP-BBSBroadband service IP poolsASSIGNED PAJan 27, 2010abuse@samaralan.ru
via RU-TAHION-20050519

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
Sep 2011
Current origin since
Sep 2011 · 15 yr
Origin networks
1