Sauce Labs status history
Current state: operational — “All Systems Operational” per https://status.saucelabs.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Sauce Labs incidents last?
From 40 incidents with a vendor-posted start and resolve time. Longest on record: 2026-February-23 Service Incident — 5.2 h (2026-02-23 17:22 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (40)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-16 11:08 UTC | 2026-September-16 Service Incident | resolved | none | 0 min |
| 2026-09-02 09:39 UTC | 2026-September-02 Service Incident | resolved | none | 2 h 13 min |
| 2026-08-25 12:33 UTC | 2026-August-25 Service Incident | postmortem | none | 45 min |
| 2026-08-07 12:08 UTC | 2026-August-07 Service Incident | postmortem | none | 57 min |
| 2026-07-16 13:00 UTC | 2026-July-16 Resolved Service Incident - Error Reporting (Backtrace) | postmortem | none | 0 min |
| 2026-07-14 23:30 UTC | 2026-July-15 Resolved Service Incident - Error Reporting (Backtrace) | postmortem | none | 0 min |
| 2026-07-14 17:19 UTC | 2026-July-14 Service Incident | postmortem | major | 3 h 03 min |
| 2026-07-01 17:02 UTC | 2026-July-1 Resolved Service Incident 1 | postmortem | minor | 0 min |
| 2026-07-01 12:12 UTC | 2026-July-01 Service Incident | postmortem | none | 45 min |
| 2026-06-24 16:39 UTC | 2026-June-24 Resolved Service Incident | postmortem | none | 0 min |
| 2026-06-18 05:30 UTC | 2026-June-18 Service Incident | postmortem | major | 1 h 28 min |
| 2026-06-01 14:02 UTC | 2026-June-1 Service Incident | postmortem | critical | 4 h 22 min |
| 2026-05-21 14:53 UTC | 2026-May-13 Resolved Service Incident | postmortem | none | 0 min |
| 2026-04-24 16:33 UTC | 2026-April-23 Resolved Service Incident | postmortem | major | 0 min |
| 2026-04-16 10:10 UTC | 2026-April-16 Resolved Service Incident | postmortem | none | 0 min |
| 2026-04-07 15:02 UTC | 2026-April-07 Service Incident | postmortem | major | 1 h 10 min |
| 2026-03-24 17:36 UTC | 2026-March-24 Resolved Service Incident | postmortem | none | 0 min |
| 2026-03-19 09:51 UTC | 2026-March-19 Service Incident | postmortem | major | 1 h 02 min |
| 2026-03-13 14:30 UTC | 2026-March-13 Resolved Service Incident | postmortem | none | 0 min |
| 2026-03-10 18:46 UTC | 2026-March-10 Service Incident | postmortem | major | 4 h 48 min |
| 2026-03-06 21:38 UTC | 2026-March-6 Resolved Service Incident | postmortem | none | 0 min |
| 2026-02-27 18:42 UTC | 2026-February-27 Service Incident | postmortem | minor | 1 h 33 min |
| 2026-02-23 17:22 UTC | 2026-February-23 Service Incident | postmortem | major | 5 h 09 min |
| 2026-01-29 17:30 UTC | 2026 - January - 29 Resolved Service Incident | postmortem | none | 0 min |
| 2026-01-29 11:11 UTC | 2026-January-29 Resolved Service Incident | postmortem | none | 0 min |
| 2026-01-13 10:43 UTC | 2026-January-13 Service Incident | postmortem | major | 7 min |
| 2026-01-05 21:15 UTC | 2026-January-5 Service Incident | postmortem | major | 1 h 08 min |
| 2025-12-18 05:30 UTC | 2025-December-18 Resolved Service Incident | postmortem | none | 0 min |
| 2025-12-17 10:30 UTC | 2025-December-17 Resolved Service Incident | postmortem | none | 0 min |
| 2025-11-19 18:54 UTC | 2025-November-19 Service Incident | postmortem | minor | 3 h 22 min |
| 2025-11-04 08:02 UTC | 2025-November-04 Service Incident | postmortem | minor | 3 h 07 min |
| 2025-11-03 16:00 UTC | 2025-November-3 Resolved Service Incident | postmortem | minor | 0 min |
| 2025-10-29 09:27 UTC | 2025-October-29 Service Incident | postmortem | critical | 1 h 20 min |
| 2025-10-28 14:07 UTC | 2025-October-28 Resolved Service Incident | postmortem | none | 2 h 06 min |
| 2025-10-28 12:53 UTC | 2025-October-28 Service Incident | postmortem | major | 1 h 29 min |
| 2025-10-28 11:30 UTC | 2025-October-28 Resolved Service Incident 1 | postmortem | none | 0 min |
| 2025-10-01 01:00 UTC | 2025-October-1 Resolved Service Incident | postmortem | none | 0 min |
| 2025-09-19 05:30 UTC | 2025-September-19 Resolved Service Incident | resolved | none | 0 min |
| 2025-09-03 16:34 UTC | 2025-September-3 Service Incident | postmortem | major | 35 min |
| 2025-08-19 19:00 UTC | 2025-August-19 Resolved Service Incident | postmortem | none | 0 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Sauce Labs with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"sauce-labs"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}