Skip to main content
Use Language & region to change the language the app shows. Use Proxy location only when servers must see traffic from another country. By default, BugRadar runs connect to the internet from the United States. If your app works only in some countries, it may block those runs or show a “not available in your region” page. You can choose a country for a run. All of the run’s browser or device traffic then leaves from a residential IP address in that country, instead of from BugRadar’s runner IPs.

Time zone without a location

Runs without a location use US Pacific time (America/Los_Angeles) on every platform: web browsers, Android emulators and iOS simulators. Physical devices and devices on your own machine keep their own time zone. On web and Android emulators, a language with a country uses that country’s time zone instead.

What it supports

Countries use two-letter ISO codes, such as MX for Mexico. Lowercase codes are accepted and changed to uppercase. Uninhabited territories (AQ, BV, HM, TF, UM) and sanctioned countries (CU, IR, KP, SY) are not available.

Choose a location

When you choose no location, the run uses the default: the United States.

In the dashboard

The Proxy location picker shows for web apps and Android emulators.
  • Run dialog: under Run options, open Proxy location and choose a country. It shows Off until you do. The Run button then names the country, for example Run from Mexico, unless the run’s language names a country.
  • Automations: in the automation editor, open Proxy location, under the browser or device picker, and choose a country. Every run the automation starts uses it.
Under the picker, a line says what the proxy changes for that run. Reruns and automatic retries keep the location of the original run.

With the CLI

With the GitHub Action

Add location to the BugRadar GitHub Action step. Every run the upload starts uses it, including the tests the step selects.

With the API

Send location in the request body of these calls:

With MCP

These MCP tools take a location argument:
  • flows_run
  • suites_run
  • labels_run
  • folders_run
  • automations_create
  • automations_update
On automations_update, an empty string removes the saved location.

Build uploads

An upload can carry a location. It applies to every run the upload starts:
  • CI/CD automations. The upload’s location replaces the automation’s own location. If the upload has none, the automation uses its own.
  • Later PR test runs against that build.
Send location to Upload Web Build for web, or to Confirm Upload for Android. The GitHub Action’s location input does this for you. iOS uploads cannot carry a location yet. If the upload starts an automation that runs on an Android real device, that run is refused.

When a run starts

Before the test starts, the run checks that its traffic leaves from the chosen country.
  • If the check passes, the browser console log records the IP: [BugRadar location] Exit IP <ip> (MX).
  • If the check fails, the run fails with an error that starts with Location proxy unavailable. A run with a location never falls back to a US IP.
For Android, the exit-IP check runs inside the device after it boots. Its result is not in the run log. This start check is the only check that can fail the run. A run with a location also moves the GPS position to the chosen country, unless its language names a country: then the language’s country decides the time zone and location, and only the IP address follows the proxy. Otherwise, a run with a location sets the time zone to the exit IP’s zone: the browser’s zone for web, and the device’s zone for Android, set before your app opens. In countries with several time zones, such as MX, this is the exit IP’s region. If the exit IP’s zone can’t be found, the run uses US Pacific time. The time zone is set once, at the start, and does not change if the IP changes. The browser’s or device’s language does not change. To change it, use Language & region.

Combinations BugRadar refuses

A request with a location is refused for:
  • an environment that uses a private network
  • an MCP flows_run call with branch_name
  • onboarding runs
  • iOS runs and physical devices (coming later)
  • mobile runs on a local device
  • an unknown or unavailable country code, such as KP (the error lists the valid codes)

Limits

  • Hooks keep BugRadar’s fixed IP. Hook scripts do not use the run’s location. If a hook calls an API that blocks US traffic, that API still refuses the call. See Network Allowlist.
  • Allowlists of BugRadar’s IPs block location runs. If your app or an API it calls accepts only BugRadar’s web runner IPs (flow_runners.virtual_runners.web_browsers on Network Allowlist), it blocks every location run.
  • The IP can change during a run. The residential IP can drop out during a run. When it changes, the run continues. For web runs, the browser console log records [BugRadar location] Exit IP changed to <ip> (<country>). BugRadar does not check the new IP’s country.
  • Android location runs start about 30 s slower, because the device boots through the proxy.
  • UDP traffic other than DNS is blocked during an Android location run (for example QUIC and WebRTC media).
  • ping (ICMP) from the device does not go through the location.
  • If the connection to the location drops during a run, the device’s requests fail until the run ends. The run is never moved to a US IP.