Data as of Nov 10, 2026

92.50.166.0/23

4 residential-proxy exits · 30 days

JSC 'Ufanet'

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

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

125 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
92.50.166.0/2403
92.50.167.0/2401

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Shifter
  • SwiftProxy
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.50.128.0/18
since Apr 2008
AS24955Residential169
20 always on
JSC "Ufanet"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
92.50.128.0/1816,384RU-ZAODS-20071218JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PADec 18, 2007abuse@ufanet.ru
└ 92.50.160.0/198,192UBNJSC "Ufanet"ASSIGNED PAMar 4, 2008abuse@ufanet.ru
via RU-ZAODS-20071218

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

92.50.164.0/22

Routing history

Pattern
Stable
First seen
Apr 2020
Current origin since
Apr 2020 · 6.6 yr
Origin networks
1