Sauce Labs incident

2026-February-23 Service Incident

Major Resolved View vendor source →
Started
Feb 23, 2026, 05:22 PM UTC
Resolved
Feb 23, 2026, 10:31 PM UTC
Duration
5h 9m
Detected by Pingoru
Feb 23, 2026, 05:22 PM UTC

Affected components

US-WestUS-WestUS-WestUS-WestUS-West

Update timeline

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Looking to track Sauce Labs downtime and outages?

Pingoru polls Sauce Labs's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Sauce Labs reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Sauce Labs alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Sauce Labs for free

5 free monitors · No credit card required