Is Sauce Labs Down?

No — Sauce Labs is up

Reachable from all 8 checked regions

Average response time: 144ms

Last checked 6 hours ago · checks run every 6 hours

Official status page: https://status.saucelabs.com

Sauce Labs uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

170ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 48 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

48-day clean streak

Sep 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

135ms

DNS 17ms TCP 5ms TLS 9ms TTFB 107ms

arn

169ms

DNS 70ms TCP 5ms TLS 8ms TTFB 141ms

cdg

111ms

DNS 39ms TCP 2ms TLS 7ms TTFB 97ms

ord

293ms

DNS 48ms TCP 21ms TLS 23ms TTFB 190ms

sin

120ms

DNS 53ms TCP 2ms TLS 4ms TTFB 111ms

sjc

154ms

DNS 31ms TCP 9ms TLS 12ms TTFB 101ms

syd

50ms

DNS 7ms TCP 1ms TLS 4ms TTFB 42ms

yyz

124ms

DNS 47ms TCP 1ms TLS 4ms TTFB 115ms

What Sauce Labs does

Sauce Labs runs a cloud testing platform with more than 10,000 real devices and 3,000 browser and operating system combinations, so teams can test across platforms without maintaining a device lab. It supports Selenium, Cypress, Appium and Playwright and plugs into CI systems, which is where most of its use sits: tests run automatically on every build rather than being launched by hand.

What an outage looks like

Automated test sessions fail to start or time out waiting for a device, and CI pipelines report the result as a test failure rather than an infrastructure error. Live testing sessions disconnect part-way through. Sauce Connect tunnels drop, so tests cannot reach an application that is not exposed to the internet. The dashboard will not load results, and REST API calls used to launch jobs return errors.

What to do about it

Read status.saucelabs.com and match three things: the product line, the region and the component. Automated, Live, Real Device, Virtual Mobile and Visual Testing are reported separately, each split across US-West, EU-Central and US-East. Sauce Connect, IPSec VPN and the REST API have their own rows. Before re-running a failed suite, confirm the region your tests target is healthy, or the retry fails the same way.

Is it down for everyone, or just you?

If this page says Sauce Labs is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Sauce Labs outage FAQ

My tests failed. Is it my code or Sauce Labs?

A platform incident usually surfaces as a test failure rather than as an obvious outage, which is what makes this hard to spot. Sessions that could not acquire a device, or that disconnected mid-run, are reported to your CI system as failures. If a whole suite failed at once with session or timeout errors rather than assertion errors, check the status page before investigating the code.

Is the outage affecting my region?

Check the row, not the banner. Almost every Sauce Labs component is broken out across US-West, EU-Central and US-East, and Real Device Testing, Native Framework Mobile App Testing and Visual Testing each list all three. Tests pinned to one data center can fail continuously while the same suite passes for a team configured against another region.

Why can Sauce Labs not reach my staging environment?

That is usually Sauce Connect rather than the testing platform. Sauce Connect is the tunnel that lets tests running in Sauce Labs reach an application that is not exposed to the internet, and it is listed as its own component per region, as is IPSec VPN. When the tunnel is affected, devices and browsers are healthy but have no route to the site under test.

Do Live and Automated testing fail together?

Not necessarily. The status page keeps them apart: Automated Browser Testing, Automated Virtual Mobile Device Testing and Automated Real Device Testing are separate from Live Browser Testing, Live Virtual Mobile Device Testing and Live Real Device Testing. A manual debugging session can work while the CI suite cannot get devices, or the other way round.

How we measure this

We request Sauce Labs's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Sauce Labs publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Sauce Labs goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required