LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

89.31.83.0/24

6 residential-proxy exits · 30 days

Limited Liability Company Incomsvyaz

Announcement
89.31.80.0/22
No RPKI
Announced by
AS41639
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
33
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.31.80.0/21
since May 2007
AS41639Residential48
6 always on
Limited Liability Company Incomsvyaz

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.31.80.0/212,048RU-INCOMSV-20060901Limited Liability Company Incomsvyaz (ORG-LLCI1-RIPE) · RUALLOCATED PASep 1, 2006sobolev@incomsv.ru
└ 89.31.82.0/23512INCOMSVLLC IncomsvyazASSIGNED PAMar 9, 2016sobolev@incomsv.ru
via RU-INCOMSV-20060901

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

89.31.80.0/22

Routing history

Pattern
Stable
First seen
Oct 2011
Current origin since
Jul 2022 · 4.3 yr
Origin networks
1