Sauce Labs Maintenance Window
We are actively working with our third-party provider to resolve an issue affecting access to the Sauce Labs UI in EU-Central-1 Data Center. This message will remain in place until normal operations resume. Thank you for your patience while we work toward a resolution.

2026-February-23 Service Incident

Incident Report for Sauce Labs

Postmortem

Dates:

Monday, February 23rd 2026, 17:22 UTC - 22:31 UTC

What happened:

WDIO-based tests run by customers using Sauce Connect 4 could not be started.

Why it happened:

Misconfiguration caused failing health checks in some cases, causing customer tunnels to shut down.

How we fixed it:

Misconfiguration was corrected.

What we are doing to prevent it from happening again:

Evaluation of the underlying software stack. 

Customers who are still using SC4 that can migrate to SC5 should do so at their earliest convenience.

Posted Apr 15, 2026 - 22:32 UTC

Resolved

We have identified the root cause and deployed a fix for this issue. All services are fully operational.
Posted Feb 23, 2026 - 22:31 UTC

Update

We have identified the root cause and are working on implementing a fix. We are continuing to investigate.
Posted Feb 23, 2026 - 19:40 UTC

Investigating

We are seeing an increase in automated tests using Sauce Connect failing with “Misconfigured -- No active tunnel found for provided identifier” errors in the US-West-1 data center. We are actively investigating.
Posted Feb 23, 2026 - 17:22 UTC
This incident affected: Automated Browser Testing (US-West), Automated Virtual Mobile Device Testing (US-West), Automated Real Device Testing (US-West), and Sauce Connect (US-West).