2026-August-07 Service Incident

What to do

• Check whether you use Sauce Labs in us, us-west-1, us-west1. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 58m it lasted.

  Anything that failed between 2026-08-07 12:08 UTC and 2026-08-07 13:06 UTC may need a replay.

• Subscribe to Sauce Labs's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=saucelabs works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Sauce Labs 3

1. investigatingAug 7, 2026, 12:08 PM UTC

   We are currently seeing elevated error rates for virtual desktop tests in the US-West-1 datacenter. We are currently investigating.

   provider

2. resolvedAug 7, 2026, 1:06 PM UTC

   After taking remedial action, Virtual Desktop tests are starting successfully in the US-West-1 Data center. All services are fully operational. We are closely monitoring the situation

   provider

3. postmortemAug 14, 2026, 4:43 PM UTC

   ### **Dates:** Friday, August 7th 2026, 11:00 UTC - 13:04 UTC. ### **What happened:** Windows and Intel Mac jobs in `us-west1` failed to start due to virtual machine \(VM\) allocation starvation. ### **Why it happened:** A service crash loop left VMs in an allocated but unclaimed state, while a cleanup bug prevented the system from releasing the orphaned capacity to boot new VMs. ### **How we fixed it:** Restored service stability and cleared stale allocations to resume VM provisioning and clear queued jobs. ### **What we are doing to prevent it from happening again:** Fixing allocator cleanup logic, strengthening deployment health checks, and improving capacity accounting for stale allocations.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.