Resolved after 5 hours 9 minutes, affecting US-West and US-West and 1 more, on February 23, 2026.
### **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.
Affected components
Update timeline
- investigating Feb 23, 2026, 05:22 PM UTC
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.
- investigating Feb 23, 2026, 07:40 PM UTC
We have identified the root cause and are working on implementing a fix. We are continuing to investigate.
- resolved Feb 23, 2026, 10:31 PM UTC
We have identified the root cause and deployed a fix for this issue. All services are fully operational.
- postmortem Apr 15, 2026, 06:58 PM UTC
### **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.
Your product runs on more than Sauce Labs
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services