Data as of Nov 15, 2026

185.13.176.0/22

1,020 residential-proxy exits · 30 days

Omskie kabelnye seti Ltd.

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

Residential-proxy exits

Proxy exits
1,020
>99% of its addresses · 30 days
Always-on exits
135
13% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
52
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

717K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.13.179.0/2451254
185.13.177.0/2444255
185.13.178.0/2421255
185.13.176.0/2419255

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

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
185.13.176.0/221,024RU-OMKC-20121218Omskie kabelnye seti Ltd. (ORG-OKSL1-RIPE) · RUALLOCATED PADec 18, 2012abuse@omkc.ru
└ 185.13.176.0/23512OKC-NETOmskie kabelnye seti Ltd.ASSIGNED PAJan 16, 2013abuse@omkc.ru
via RU-OMKC-20121218
└ 185.13.178.0/23512OKC-NETOmskie kabelnye seti Ltd.ASSIGNED PAJan 30, 2013abuse@omkc.ru
via RU-OMKC-20121218

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
Dec 2012
Current origin since
Dec 2012 · 14 yr
Origin networks
1