Data as of Nov 12, 2026

80.89.11.0/24

6 residential-proxy exits · 30 days

Alexander Sbezhnev

Announcement
this exact prefix
No RPKI
Announced by
Type
Unknown
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
38
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

289 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • EZProxies
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NextProxy
  • NodeProxy
  • PSBProxy
  • PrivateByte
  • PrivateProxy
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • TrueProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.89.8.0/22
since Sep 2016
AS21105Unknown24Alexander Sbezhnev

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.0.0/204,096RU-SBEZHNEV-20010829Alexander Sbezhnev (ORG-AS1268-RIPE) · RUALLOCATED PADec 3, 2024alexvladjp@mail.ru
└ 80.89.8.0/221,024RTKPRIM-NETunknownASSIGNED PAJul 25, 2022alexvladjp@mail.ru
via RU-SBEZHNEV-20010829

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2025
Current origin since
Mar 2025 · 1.7 yr
Origin networks
1