← Back to Blog

Google Labs Unavailable in Russia: How to Access Whisk, ImageFX, and Stitch via Proxy

Google Labs blocks access to Whisk, ImageFX, and Stitch based on geolocation. We show what Google checks upon login, why a regular VPN doesn't help, and how to set up a proxy correctly.

📅November 17, 2026

Are you opening Whisk or ImageFX, and instead of generating an image, you see "This service is not available in your country"? This is not a bug or a temporary outage — Google intentionally restricts access to Labs based on the geography of the account. In this article, we will discuss what exactly Google checks when accessing Labs, why a regular free VPN is almost always banned or simply doesn't allow access, and how to set up a proxy correctly to ensure stable access, while keeping your Google account from being blocked.

What are Google Labs, Whisk, ImageFX, and Stitch

Google Labs is an experimental platform where the company tests new AI products before their mass release. Currently, there are several tools available that are actively used by marketers, designers, and SMM specialists:

  • ImageFX — image generation based on text prompts using the Imagen model, used for creating visuals for advertising creatives and social media posts.
  • Whisk — a tool for remixing images: upload a reference, get variations in different styles, convenient for quickly adapting creatives for A/B tests.
  • Stitch — an AI generator for interfaces and UI mockups from text descriptions, useful for product teams and freelancers who create quick prototypes for clients.

The problem is that all three products are launched in waves by region. First, access is opened in the USA, then in parts of Europe and Asia, while in Russia, Belarus, parts of the CIS countries, and the Middle East, access is either completely unavailable or appears with a significant delay. Meanwhile, the Google account itself can be fully operational — Labs simply detects the geolocation and denies access.

Why these tools are unavailable in your country

There are three main reasons why Google restricts access geographically, and understanding these reasons directly affects how you will bypass the block.

Legal and regulatory restrictions. In several countries, there are sanctions regimes or local legislation regarding AI content, which is why Google does not officially provide the service. Here, the company takes precautions and blocks access at both the account and IP levels simultaneously.

Gradual rollout of capabilities. Image and interface generation requires significant GPU resources. Google opens access gradually to avoid overloading the infrastructure, prioritizing users from key markets — usually the USA, UK, EU countries, and some regions of Asia.

Local language and content policy. For some countries, Google restricts the type of generated content or completely disables the service until moderation is adapted to local legislation.

For the user, the outcome is the same: you open labs.google, see the interface, but when trying to generate anything — you get a refusal marked as unavailable in the region. And the only legal way to change the visible Google geolocation is to connect through an IP from another country.

What exactly Google checks upon entry

To understand why simply "turning on the VPN" doesn't always work, you need to know what signals Google collects with each request to Labs. This is not just one parameter, but a whole chain of checks, and if even one element does not match the expected, the system may either block access or — worse — flag the account as suspicious.

Parameter What Google checks
IP address Determines the country and type of network: home, mobile, data center, or known VPN pool
WebRTC Can reveal the real local IP even when a proxy or VPN is enabled
DNS requests If DNS queries go through the provider instead of the proxy — a regional leak occurs (DNS leak)
Time zone and system language Cross-referenced with the declared geolocation of the IP, discrepancies increase risk score
Google account region Tied to the country at registration, settings in myaccount.google.com
Login history A sudden change of region for an "old" account looks suspicious
IP reputation Known public VPN ranges and data centers are often blacklisted by Google

It is this combination of factors that determines whether Google will allow you into Labs or not. A single suitable IP without the other settings guarantees almost nothing.

Why a regular VPN doesn't help and bans accounts

Mass-market free and even paid consumer VPN services use the same pool of IP addresses for thousands of users simultaneously. Google is well aware of these ranges: as soon as a request to Labs comes from such an IP, the system immediately flags it as VPN traffic and either blocks the specific session or requires additional account verification — phone confirmation, CAPTCHA, and sometimes temporary freezing.

The second problem is the instability of geolocation. Many VPN clients change the exit node with each reconnection, causing Google to see that the same account is logging in from the Netherlands one moment and from Singapore the next within the same hour. For security systems, this is a classic pattern of account hacking, and the reaction is — blocking or forced logout from all devices.

The third problem is WebRTC and DNS leaks. Most free VPN browser extensions do not fully close these leaks, and Google still sees the user's real region through alternative channels, even if the visible IP is already "correct."

Therefore, the approach of "turned on the VPN — logged into Whisk" works inconsistently: sometimes it lets you in, sometimes it bans the session, and with frequent use, it can lead to a temporary block of the Google account itself due to suspicious activity.

Which type of proxy actually provides access

For Google to see you as a regular user from the desired country, and not as VPN traffic, it is important not just to change the IP, but also the type and quality of that IP. Let's break down three main options.

Type of Proxy How Google sees it Suitable for Labs
Data center proxies Hosting provider range, easily identified as a "non-residential" IP Low likelihood of access, high risk of blocking
Residential proxies Real IP from a home provider in a specific country High, the main working option for Whisk, ImageFX, Stitch
Mobile proxies IP from a mobile operator, shared pool among thousands of real subscribers High, but less stable session due to IP changes by the operator

For most scenarios working with Google Labs, residential proxies tied to the desired country with a sticky session feature are optimal — this is when the IP does not change for a specified time, for example, 10-30 minutes, which is enough for smooth generation in ImageFX or working in Stitch without session interruptions.

Data center proxies are almost useless for this task: Google knows the ranges of major hosting providers too well and blocks them at the Labs level even before checking the region. They should only be considered for less sensitive tasks — for example, scraping publicly available data, where account geolocation is not critical.

Step-by-step proxy setup for Google Labs

Let's discuss the setup using an anti-detect browser as an example, as this is the most reliable way to isolate the Google account session from the rest of the profile and avoid fingerprint conflicts. Dolphin Anty, AdsPower, Octo Browser, or GoLogin will work — the setup logic is similar everywhere.

  1. Create a separate profile for working with the Google account — do not use the main profile with other services to avoid mixing fingerprints and history.
  2. Select the proxy geolocation that matches the country where Labs is already available — most often this is the USA or the UK for ImageFX, Whisk, and Stitch.
  3. Insert the proxy data in the profile settings: address, port, username, and password, protocol type — usually HTTP(S) or SOCKS5.
  4. Enable sticky session for 20-30 minutes, so the IP does not change during image generation and Google does not see geolocation jumps.
  5. Set the time zone and browser language according to the selected country — in most anti-detect browsers, this is done automatically when specifying geo proxy, but it is worth checking manually.
  6. Check for leaks using the built-in checker of the anti-detect browser or a third-party IP, WebRTC, and DNS checking service — all three parameters should show the same country.
  7. Log into your Google account through this profile and only after a successful login open labs.google and the desired tool — Whisk, ImageFX, or Stitch.
  8. Work within a single session, without switching IPs in the middle of work — this reduces the risk of re-verifying the account.

If you are not using an anti-detect browser and are working through regular Chrome or Firefox, you can set the proxy through an extension or system network settings, but in this case, make sure to manually disable WebRTC — browsers do not block it by default.

Common mistakes and how to avoid them

Using one IP for multiple Google accounts. If you log into different accounts sequentially through the same proxy, Google may link them together and apply restrictions to all of them, especially if one of the accounts has already received complaints or temporary blocks.

Changing geolocation in the middle of an active session. If you started generating in Whisk with an IP from the USA, and five minutes later the proxy switched to an IP from Germany, Google sees abnormal movement and may interrupt the session or require re-login with identity confirmation.

Ignoring the account's region. Even with a perfect proxy, an old account with a clear tie to a country where Labs is blocked (payment methods, interface language, location history) may receive additional checks. In this case, it makes more sense to create a new account initially for the desired region rather than trying to "transfer" the old one.

Using free public proxy lists. Such IPs are often already blacklisted by Google due to mass usage by bots, so access may either not open at all or close after the first generation.

Lack of connection speed checks. ImageFX and Stitch send fairly heavy requests with an expectation of a response from the GPU cluster, and if the proxy is slow or has high latency, the request may simply not reach, and the system mistakenly shows a message about the service being unavailable in the region instead of the real reason — a timeout.

Checklist before launching

  • A residential or mobile IP from the desired country is selected, not a data center
  • A sticky session is enabled for at least 20-30 minutes
  • WebRTC, DNS, and IP have been checked — all show the same country
  • The time zone and browser language match the geo proxy
  • A separate profile in the anti-detect browser is used for the account
  • One proxy is assigned to one Google account, without cross-usage
  • The account was initially created or adapted for the desired region

Conclusion

Google Labs restricts access to Whisk, ImageFX, and Stitch based on a combination of signals: IP, WebRTC, DNS, time zone, and the region of the account itself. A regular VPN only addresses the first part of the task and often highlights other discrepancies, causing access to either not open or the account to be subjected to checks. A stable result is achieved by combining a quality IP from the desired country, correct system settings in the browser, and isolating the profile for a specific account.

If you regularly test Google Labs or other geo-restricted AI tools, the best option is to use residential proxies tied to the country and supporting sticky sessions — they minimize the risk of blocking and provide access that closely resembles the behavior of a real user from the desired region.