Sauce Labs incident

2026-April-07 Service Incident

Resolved after 1 hour 10 minutes, affecting US-West and US-West and 1 more, on April 7, 2026.

postmortem Apr 10, 2026, 09:56 PM UTC

### **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.

Started
Apr 07, 2026, 03:02 PM UTC
Resolved
Apr 07, 2026, 04:13 PM UTC
Duration
1h 10m
Detected by Pingoru
Apr 07, 2026, 03:02 PM UTC

Affected components

US-WestUS-WestUS-WestUS-WestEU-CentralEU-CentralEU-CentralEU-Central

Update timeline

  1. investigating Apr 07, 2026, 03:02 PM UTC

    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. resolved Apr 07, 2026, 04:13 PM UTC

    We have identified the root cause and have deployed a fix for this issue. All services are fully operational.

  3. postmortem Apr 10, 2026, 09:56 PM UTC

    ### **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.

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 →