Sauce Labs incident

2026-February-27 Service Incident

Resolved after 1 hour 33 minutes, affecting US-West, on February 27, 2026.

postmortem Apr 15, 2026, 07:06 PM UTC

### **Dates:** Friday, February 27th 2026, 16:15 UTC - 19:50 UTC ### **What happened:** Requests made using API client authentication would return 500 errors. ### **Why it happened:** An internal data structure became corrupted due to a race condition. ### **How we fixed it:** The affected service was restarted, and a long-term fix was applied. ### **What we are doing to prevent it from happening again:** Thread locking has been applied to the affected service.

Started
Feb 27, 2026, 06:42 PM UTC
Resolved
Feb 27, 2026, 08:15 PM UTC
Duration
1h 33m
Detected by Pingoru
Feb 27, 2026, 06:42 PM UTC

Affected components

US-West

Update timeline

  1. investigating Feb 27, 2026, 06:42 PM UTC

    Live and automated real device test results are not being displayed on the test results page in the US-West-1 data center. We are investigating.

  2. resolved Feb 27, 2026, 08:15 PM UTC

    After taking remedial action, we are now seeing real device test results display in the US-West-1 data center. All services are fully operational.

  3. postmortem Apr 15, 2026, 07:06 PM UTC

    ### **Dates:** Friday, February 27th 2026, 16:15 UTC - 19:50 UTC ### **What happened:** Requests made using API client authentication would return 500 errors. ### **Why it happened:** An internal data structure became corrupted due to a race condition. ### **How we fixed it:** The affected service was restarted, and a long-term fix was applied. ### **What we are doing to prevent it from happening again:** Thread locking has been applied to the affected service.

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.

Add your stack →