Resolved after 45 minutes, on July 1, 2026.
### **Dates:** Wednesday July 1st 2026, 09:37 – 12:46 UTC ### **What happened:** The Appium Inspector feature, used during real device live testing sessions, became unavailable after a scheduled UI deployment. Users who attempted to use the feature during a live test were presented with a 500 error, disrupting their active testing session. Automated test pipelines were not affected. ### **Why it happened:** A routine upgrade of a core frontend library introduced an incompatibility with the Appium Inspector's rendering logic. The previous library version tolerated the pattern, but the updated version did not. The issue was not caught before deployment due to insufficient end-to-end test coverage for this specific feature. ### **How we fixed it:** We rolled back the UI to the last known working version to restore the feature immediately, and then deployed a targeted fix for the incompatibility. ### **What we are doing to prevent it from happening again:** We are adding end-to-end test coverage for the Appium Inspector feature to ensure it is validated automatically before future deployments.
Update timeline
- investigating Jul 01, 2026, 12:12 PM UTC
We are experiencing an issue with accessing Appium Inspector in the US-West-1, EU-Central-1, and US-East-4 data centers. We are investigating.
- resolved Jul 01, 2026, 12:58 PM UTC
We have identified the root cause and have deployed a fix for this issue. All services are fully operational.
- postmortem Jul 20, 2026, 08:34 PM UTC
### **Dates:** Wednesday July 1st 2026, 09:37 – 12:46 UTC ### **What happened:** The Appium Inspector feature, used during real device live testing sessions, became unavailable after a scheduled UI deployment. Users who attempted to use the feature during a live test were presented with a 500 error, disrupting their active testing session. Automated test pipelines were not affected. ### **Why it happened:** A routine upgrade of a core frontend library introduced an incompatibility with the Appium Inspector's rendering logic. The previous library version tolerated the pattern, but the updated version did not. The issue was not caught before deployment due to insufficient end-to-end test coverage for this specific feature. ### **How we fixed it:** We rolled back the UI to the last known working version to restore the feature immediately, and then deployed a targeted fix for the incompatibility. ### **What we are doing to prevent it from happening again:** We are adding end-to-end test coverage for the Appium Inspector feature to ensure it is validated automatically before future deployments.
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.
Amazon Web Services