Skip to content
OutageDeck

Incident detail

2026-April-07 Service Incident

Resolved incidentMajor

Timeline window

to

Outage alerts

Get alerted the next time Sauce Labs breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Sauce Labs alerts work

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

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

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

  3. Resolved

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