checked Sep 11, 2026 4:23 PM UTC · Sauce Labs's official status page
Sauce Labs is up and running.
All components operational
Statusfield watches Sauce Labs alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
5 reports published by Sauce Labs in the last 30 days
When Sauce Labs breaks, it is typically resolved in 1h 49m — median across 2 resolved incidents over 90 days.
resolvedSep 2 · 11:53 UTC
After taking remedial action, Real Device test error rates have returned to normal in the EU-Central-1 data center. All services are fully operational.
Reported by Sauce Labs on their status page.
postmortemSep 3 · 20:23 UTC
Tuesday August 25th 2026, 11:38 – 13:10 UTC
Customers running macOS and iOS tests in our US-West region experienced degraded service. Roughly 50% of the virtual Mac capacity in the region stopped accepting new tests, so tests either queued or failed to start. Remaining capacity came under additional pressure as work shifted onto it, which extended start times for both desktop and simulator tests.
An internal security certificate used by our Mac hosts to reach a supporting cloud service reached its expiry date. Once it lapsed, the hosts could no longer establish a trusted connection to that service and stopped provisioning new test machines. The certificate had been issued manually and had neither automated renewal nor expiry alerting.
We issued and deployed a replacement certificate, which restored connectivity and returned Mac capacity to normal levels.
We are moving these certificates onto automated renewal and adding alerting so they are replaced well ahead of expiry, along with reviewing the surrounding tooling to make certificate handling safer.
Reported by Sauce Labs on their status page.
postmortemAug 14 · 16:43 UTC
Friday, August 7th 2026, 11:00 UTC - 13:04 UTC.
Windows and Intel Mac jobs in us-west1 failed to start due to virtual machine (VM) allocation starvation.
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.
Restored service stability and cleared stale allocations to resume VM provisioning and clear queued jobs.
Fixing allocator cleanup logic, strengthening deployment health checks, and improving capacity accounting for stale allocations.
Reported by Sauce Labs on their status page.
postmortemAug 14 · 16:48 UTC
Thursday July 16th 2026, 13:03 – 17:33 UTC
Symbol archives uploaded in multiple parts failed to process. All regions were affected.
Our symbol processing service sent an upload-verification field that our cloud storage provider's API does not accept for multi-part uploads, so those uploads were rejected. A fix for this had already been developed, but it had not yet been included in a released build and the service was not configured to use it. As in the first incident, rejected uploads were retried and accumulated on local disk.
We deployed a build containing the fix and corrected the service configuration on the affected workers. A large backlog of uploads then processed, which briefly re-filled the disks before draining completely.
We are releasing the fix formally through our build pipeline and persisting the corrected configuration in our configuration management, so it can't be lost. The disk-utilization alerting added after the first incident also covers the disk-exhaustion pattern common to both.
Reported by Sauce Labs on their status page.
postmortemAug 14 · 16:47 UTC
Tuesday July 14th 2026, 23:45 UTC – Wednesday July 15th 2026, 23:05 UTC
Symbol archive uploads to Error Reporting (Backtrace) projects failed with HTTP 400 errors. All regions were affected.
The credentials our symbol processing service used to write to cloud storage were no longer valid, so uploads could not be stored. Failed uploads were retried repeatedly and accumulated on local disk until the service ran out of space, at which point it also began rejecting new uploads.
We reissued the storage credentials, increased disk capacity on the affected workers, and restarted the service. The queued uploads then processed successfully, and we confirmed recovery with affected customers.
We've added disk-utilization monitoring and alerting to this service so we detect the condition ourselves before it affects uploads, rather than relying on customer reports.
Reported by Sauce Labs on their status page.
