Tricentis incident
Customers may experience performance issues in multiple regions
Tricentis experienced a minor incident on April 30, 2026 affecting US-EAST-1 | Region 1 and AP-SOUTHEAST-2 | Region 8 and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 30, 2026, 11:25 AM UTC
Status: Identified We have identified the root cause of the issue that is causing graceful degradation in all U.S. based regions and APAC. We’ll continue to share updates as we make progress. Affected components US-EAST-2 | Region 13 (Degraded performance) US-WEST-2 | Region 7 (Degraded performance) US-EAST-1 | Region 1 (Degraded performance) AP-SOUTHEAST-2 | Region 8 (Degraded performance)
- monitoring Apr 30, 2026, 11:35 AM UTC
Status: Monitoring A fix has been implemented in all regions and we are currently monitoring the system to ensure everything is working as expected. Affected components US-EAST-2 | Region 13 (Operational) US-WEST-2 | Region 7 (Operational) US-EAST-1 | Region 1 (Operational) AP-SOUTHEAST-2 | Region 8 (Operational)
- resolved Apr 30, 2026, 12:19 PM UTC
Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-WEST-2 | Region 7 (Operational) US-EAST-1 | Region 1 (Operational) AP-SOUTHEAST-2 | Region 8 (Operational) US-EAST-2 | Region 13 (Operational)