What is the TestingBot Selenium hub URL?

The Selenium and Appium hub endpoint is https://hub.testingbot.com/wd/hub. Pass your API key and secret inside the tb:options capability map for W3C-compliant clients (Selenium 4 and later). See the Selenium support page for full configuration examples.

Which IP ranges do TestingBot tests come from?

The current list of TestingBot grid IP ranges is published on this page and via the REST API ipranges endpoint . Use it to allowlist TestingBot traffic on firewalls in front of staging or production environments.

What is the default idle timeout on TestingBot?

The default idle timeout is 130 seconds. TestingBot will end a test session if no new WebDriver command is received within that window. Change it per-test with the idleTimeout capability , or read about it in the test errors reference .

What is the default screen resolution on the grid?

The default desktop screen resolution is 1280x1024. Override it per-test with the screenResolution capability . Common resolutions (1920x1080, 1440x900, etc.) are supported on all desktop browsers.

Which Appium version does TestingBot use?

TestingBot automatically selects the most recent Appium version that is compatible with the device, OS and OS version you request. To pin a specific version, set the appiumVersion capability . See supported Appium versions for the full list.

Which Playwright or Puppeteer version does TestingBot use?

TestingBot uses the same Playwright or Puppeteer version as the one you are using on the client side, ensuring full compatibility. There is no fixed server-side version pin.

Does TestingBot support geolocation testing from different countries?

Yes. Set the geoCountryCode capability (see the geolocation testing docs ) to route browser traffic through an egress IP in your chosen country. The current list of egress IPs per country is published below.

TestingBot Grid Configuration

TestingBot provides a distributed cloud grid of real browsers and devices. Connect your Selenium, Appium, Puppeteer, Playwright, Cypress, XCUITest and Espresso tests to this grid through the endpoints documented below.

The Selenium and Appium grid runs the latest stable Selenium 4 server and is fully W3C-compliant. Your client SDK version (Selenium, Appium, Playwright, Puppeteer) is matched on the grid side for compatibility.

Service status

Live incidents and scheduled maintenance are posted on the TestingBot status page (RSS feed available). Subscribe to the status page to receive notifications for grid availability, hub-endpoint issues and tunnel infrastructure events.

Uptime report for testingbot.com: last 30 days

Uptime report for Selenium grid: last 30 days

TestingBot IP Ranges

Below you will find an up-to-date list of the TestingBot IP ranges used during testing.

109.68.162.161
109.68.162.165
78.20.187.211
162.55.135.22
95.217.83.184
95.216.39.110
95.216.229.109
142.132.137.7
195.201.167.43
162.55.24.100
185.223.133.13

You can also fetch this up-to-date list from the TestingBot REST-API.

Geolocation IP ranges

TestingBot provides geolocation testing, allowing you to test from various geographical places around the world. Below are the IP addresses we use for this.

AU Australia: 35.213.216.75
BE Belgium: 109.68.162.161
BR Brazil: 35.215.244.91
CA Canada: 34.47.9.124
CL Chile: 34.176.132.166
FR France: 15.236.216.234
DE Germany: 188.245.92.209
IN India: 35.207.203.231
IT Italy: 15.161.57.62
JP Japan: 35.213.44.184
NO Norway: 51.120.9.213
SG Singapore: 18.138.255.42
ZA South Africa: 13.245.163.253
SE Sweden: 16.171.19.152
CH Switzerland: 34.65.52.54
AE United Arab Emirates: 20.174.25.155
GB United Kingdom: 35.214.33.251
US United States: 178.156.132.19

Selenium grid configuration

W3C-compliant Selenium 4 endpoint. Connect your Selenium WebDriver client (Java, Python, Ruby, Node.js, C#, PHP) to the URL below and pass your API key and secret inside the tb:options capability map.

Key	Value
Selenium version	Latest stable Selenium 4 (W3C protocol). The grid is fully W3C-compliant. Pin a specific Selenium version with the seleniumVersion capability if needed.
Hub endpoint	`https://hub.testingbot.com/wd/hub`
Port	443 (HTTPS, recommended). Plain HTTP on port 80 and 4444 is also accepted but not recommended for production.
Default idle timeout	130 seconds. Change the idleTimeout capability to raise or lower this per test.
Default screen resolution	1280x1024. Change the screenResolution capability to pick a different resolution per test.

Appium grid configuration

Appium 2 endpoint for native mobile app testing and mobile-browser testing on iOS and Android simulators, emulators and real devices. Uses the same hub URL as Selenium.

Key	Value
Appium version	Latest compatible Appium version for the specified device, OS and OS version. Pin a specific Appium version with the appiumVersion capability.
Hub endpoint	`https://hub.testingbot.com/wd/hub`
Port	443 (HTTPS, recommended). Plain HTTP on port 80 and 4444 is also accepted but not recommended for production.
Default idle timeout	130 seconds. Change the idleTimeout capability per test if needed.

Puppeteer and Playwright configuration

Puppeteer and Playwright connect over a WebSocket endpoint rather than the WebDriver HTTP hub. Use the appropriate wss:// URL below and pass your API key, secret, browserName and browserVersion as query parameters or capabilities depending on your client. See the Playwright support page and the Puppeteer support page for complete examples.

Key	Value
Playwright endpoint	`wss://cloud.testingbot.com/playwright`
Puppeteer endpoint	`wss://cloud.testingbot.com/puppeteer`
Playwright or Puppeteer version	TestingBot matches the server-side version to the client-side version you use, ensuring full compatibility. No version pin is needed on the capabilities.
Port	443 (TLS-encrypted WebSocket). Plain ws:// on port 80 is also accepted but not recommended for production.