# 2026-July-16 Resolved Service Incident - Error Reporting (Backtrace)

- Provider: [Sauce Labs](https://down.guide/providers/saucelabs)
- Confidence: Confirmed
- Impact: Operational
- lasted 0m
- started 2026-07-16 20:33 UTC
- id: DWN-fbef87fa7f
- Official page: https://stspg.io/vs92t5j754q8

## Updates from Sauce Labs
### 2026-07-16 13:00 UTC: resolved
Between July 16th 13:03 UTC and July 16th 17:33 UTC, we experienced a service disruption where symbol archives utilizing multi-part upload protocols failed to process. Incident has been resolved and all services are operational.

### 2026-08-14 16:48 UTC: postmortem
Dates:
Thursday July 16th 2026, 13:03 – 17:33 UTC
What happened:
Symbol archives uploaded in multiple parts failed to process. All regions were affected.
Why it happened:
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.
How we fixed it:
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.
What we are doing to prevent it from happening again:
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.

From the builder: does your app depend on Sauce Labs? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=saucelabs) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Sauce Labs.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-fbef87fa7f), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.