Major incident

Sauce Labs: 2026-April-07 Service Incident

Affected: US-West, US-West, US-West, US-West, EU-Central, EU-Central, EU-Central, EU-Central

Current status of Sauce Labs: Operational — live Sauce Labs status

Timeline

1. Apr 7, 2026, 15:02 UTC
   investigating
   We are currently investigating reports of test failures affecting users running tests using SauceCtl in our US-West-1 and EU-Central-1 Data Center. We are investigating.
2. Apr 7, 2026, 16:13 UTC
   resolved
   We have identified the root cause and have deployed a fix for this issue. All services are fully operational.
3. Apr 10, 2026, 21:56 UTC
   postmortem
   ### **Dates:** Monday April 7th 2026, ~11:00 – 15:55 UTC ### **What happened:** Some customers experienced 503 errors when running tests via saucectl. The test-composer service was intermittently unavailable, preventing framework-based test execution. ### **Why it happened:** A stale Docker image was deployed to the test-composer service due to a packaging issue that arose during an internal container registry migration. This caused service pods to crash. ### **How we fixed it:** We identified the stale image and redeployed the correct version, restoring the service. ### **What we are doing to prevent it from happening again:** We are hardening our image deployment pipeline and adding validation checks to ensure container registry migrations do not result in stale or incorrect images being deployed to production.

Updates as published by Sauce Labs (original).