Sauce Labs incident

2026-June-1 Service Incident

Resolved after 4 hours 22 minutes, affecting US-East and US-East and 1 more, on June 1, 2026.

postmortem Jun 15, 2026, 11:32 PM UTC

### **Dates:** Monday, June 1st 2026, 13:06 UTC - 15:42 UTC. ### **What happened:** Customers served by the US-EAST-4 region were unable to authenticate or start new test sessions because an incomplete TLS certificate chain was deployed to the core directory services. ### **Why it happened:** A certificate extraction script defect silently truncated the certificate chain after the certificate authority transitioned to a longer hierarchy. ### **How we fixed it:** Reverted the certificate rotation and re-applied the previous known ,good certificate to restore authentication services. ### **What we are doing to prevent it from happening again:** Implementing pre-deployment certificate chain validation, adding active monitoring, and fixing the script's chain-length limitations.

Started
Jun 01, 2026, 02:02 PM UTC
Resolved
Jun 01, 2026, 06:24 PM UTC
Duration
4h 22m
Detected by Pingoru
Jun 01, 2026, 02:02 PM UTC

Affected components

US-EastUS-EastUS-EastUS-EastUS-EastUS-EastUS-East

Update timeline

  1. investigating Jun 01, 2026, 02:02 PM UTC

    We are experiencing an issue where the US-EAST data center is currently unavailable. We are investigating.

  2. investigating Jun 01, 2026, 02:55 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 01, 2026, 03:30 PM UTC

    We have identified the root cause and are working on implementing a fix.

  4. monitoring Jun 01, 2026, 04:02 PM UTC

    Access has been restored to the US-EAST data center. We are monitoring.

  5. resolved Jun 01, 2026, 06:24 PM UTC

    After taking remedial action, access to the US-EAST data center is fully restored. This incident is resolved.

  6. postmortem Jun 15, 2026, 11:32 PM UTC

    ### **Dates:** Monday, June 1st 2026, 13:06 UTC - 15:42 UTC. ### **What happened:** Customers served by the US-EAST-4 region were unable to authenticate or start new test sessions because an incomplete TLS certificate chain was deployed to the core directory services. ### **Why it happened:** A certificate extraction script defect silently truncated the certificate chain after the certificate authority transitioned to a longer hierarchy. ### **How we fixed it:** Reverted the certificate rotation and re-applied the previous known ,good certificate to restore authentication services. ### **What we are doing to prevent it from happening again:** Implementing pre-deployment certificate chain validation, adding active monitoring, and fixing the script's chain-length limitations.

Your product runs on more than Sauce Labs

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →