Data as of Nov 16, 2026

92.50.188.0/22

1 residential-proxy exit · 30 days

JSC 'Ufanet'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
20
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BlurPath
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.50.128.0/18
since Apr 2008
AS24955Residential176
21 always on
JSC "Ufanet"
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
92.50.190.0/23
since Sep 2024
AS24955ResidentialJSC "Ufanet"

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
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

Summary

Routing history

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