Critical incident

Sauce Labs: 2026-June-1 Service Incident

Jun 1, 2026, 14:02 UTC
started
18:24 UTC
resolved
4 h 22 min
duration

Affected: US-East, US-East, US-East, US-East, US-East, US-East, US-East

Current status of Sauce Labs: Operational — live Sauce Labs status

Timeline

  1. Jun 1, 2026, 14:02 UTC
    investigating
    We are experiencing an issue where the US-EAST data center is currently unavailable. We are investigating.
  2. Jun 1, 2026, 14:55 UTC
    investigating
    We are continuing to investigate this issue.
  3. Jun 1, 2026, 15:30 UTC
    investigating
    We have identified the root cause and are working on implementing a fix.
  4. Jun 1, 2026, 16:02 UTC
    monitoring
    Access has been restored to the US-EAST data center. We are monitoring.
  5. Jun 1, 2026, 18:24 UTC
    resolved
    After taking remedial action, access to the US-EAST data center is fully restored. This incident is resolved.
  6. Jun 15, 2026, 23:32 UTC
    postmortem
    ### **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.

Updates as published by Sauce Labs (original).

Other services with incidents at the same time

More Sauce Labs incidents