Data as of Nov 11, 2026

80.89.192.0/20

27 residential-proxy exits · 30 days

Sibirskie Seti Ltd.

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
94% of it

Residential-proxy exits

Proxy exits
27
0.66% of its addresses · 30 days
Always-on exits
1
3.7% of its exits
Spread
11 of 16
/24s with at least one exit
Providers
68
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.2K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LUMIPROXY
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PSBProxy
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Smartproxy
  • VProxy
  • VantageProxies
  • VitalExclusive
  • 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
80.89.192.0/204,096RU-CITYNET-20081208Sibirskie Seti Ltd. (ORG-CNL7-RIPE) · RUALLOCATED PADec 8, 2008abuse@sibset-team.ru
└ 80.89.192.0/24256RU-FIRSTMILE-INFRASTRUCTURE-6LIR own needs network 6ASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.193.0/24256RU-FIRSTMILE-CUSTOMER-NET-14The address for customers at Niznya ElcovkaASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.194.0/24256RU-FIRSTMILE-CUSTOMER-NET-15'Ch' area end users networkASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.195.0/24256RU-FIRSTMILE-CUSTOMER-NET-16Ob'GES area end user networkASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.196.0/24256RU-FIRSTMILE-CUSTOMER-NET-17'VZ' area end usersASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.197.0/24256RU-FIRSTMILE-CUSTOMER-NET-18'Ch' area end users networkASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.198.0/24256RU-FIRSTMILE-CORPORATE-NET-7Corporate customers in 'VZ' areaASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.199.0/24256RU-FIRSTMILE-CUSTOMER-NET-19'Ch' area end users networkASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.200.0/24256RU-FIRSTMILE-CUSTOMER-NETOb'GES area end users networkASSIGNED PAJul 6, 2015abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.201.0/24256RU-FIRSTMILE-CUSTOMER-NET'Ch' area end users networkASSIGNED PAJul 6, 2015abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.202.0/24256RU-FIRSTMILE-CUSTOMER-NET'Vz' area end users networkASSIGNED PAJan 29, 2016abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.203.0/24256RU-FIRSTMILE-CUSTOMER-NETThe address for customers at Niznya ElcovkaASSIGNED PAJan 29, 2016abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.204.0/24256RU-FIRSTMILE-CUSTOMER-NETThe address for customers at Niznya ElcovkaASSIGNED PAJan 29, 2016abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.205.0/24256RU-CITYNET-NSKunknownASSIGNED PANov 9, 2018abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.206.0/24256RU-FIRSTMILE-CUSTOMER-NET-13Wi-Fi Public NetworkASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208
└ 80.89.207.0/24256RU-FIRSTMILE-INFRASTRUCTURE-7LIR own needs network 7ASSIGNED PAApr 6, 2012abuse@sibset-team.ru
via RU-CITYNET-20081208

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,096 addresses
TypeAddressesShareRanges
Residential3,84094%2
Business2566.3%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2009
Current origin since
Aug 2016 · 10 yr
Origin networks
2
Last change of origin
Aug 2016
Recorded history

History

Handoffs
1