Tricentis Outage History

Tricentis is up right now

Tricentis had 51 outages in the last 2 years — averaging 2.1 incidents per month.

There were 51 Tricentis outages since January 29, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tricentis.com

Minor June 17, 2026

Some sub-features of Test execution may not load properly

Detected by Pingoru
Jun 17, 2026, 02:13 PM UTC
Resolved
Jun 17, 2026, 02:13 PM UTC
Duration
—
Affected: US-EAST-1 | Region 1US-EAST-2 | Region 13
Timeline · 3 updates
  1. identified Jun 17, 2026, 01:52 PM UTC

    Status: Identified We have identified the root cause of the issue and applied a fix. We are currently monitoring the environment and awaiting confirmation that the issue has been fully resolved. We will continue to provide updates as we receive confirmation and verify system stability. Affected components US-EAST-1 | Region 1 (Degraded performance) US-EAST-2 | Region 13 (Degraded performance)

  2. monitoring Jun 17, 2026, 01:57 PM UTC

    Status: Monitoring The fix has been verified, and the issue has been resolved. We are continuing to monitor the environment to ensure stability and confirm that all services are operating normally. We will provide further updates if needed. Affected components US-EAST-2 | Region 13 (Operational) US-EAST-1 | Region 1 (Operational)

  3. resolved Jun 17, 2026, 02:13 PM UTC

    Status: Resolved The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-EAST-2 | Region 13 (Operational) US-EAST-1 | Region 1 (Operational)

Read the full incident report →

Minor June 15, 2026

Tosca SAP experiencing some features failing

Detected by Pingoru
Jun 15, 2026, 06:49 PM UTC
Resolved
Jun 15, 2026, 06:49 PM UTC
Duration
—
Affected: SAP: EuropeSAP: East US
Timeline · 3 updates
  1. investigating Jun 15, 2026, 09:42 AM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components SAP: East US (Degraded performance) SAP: Europe (Degraded performance)

  2. identified Jun 15, 2026, 09:42 AM UTC

    Status: Identified 🔍 We are currently investigating reports of an issue. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components SAP: East US (Degraded performance) SAP: Europe (Degraded performance)

  3. resolved Jun 15, 2026, 06:49 PM UTC

    Status: Resolved 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components SAP: East US (Operational) SAP: Europe (Operational)

Read the full incident report →

Minor June 11, 2026

Tosca - issue with login

Detected by Pingoru
Jun 11, 2026, 08:11 PM UTC
Resolved
Jun 11, 2026, 08:11 PM UTC
Duration
—
Affected: SAP: East US
Timeline · 4 updates
  1. investigating Jun 11, 2026, 02:04 PM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue with login page loading. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components SAP: East US (Partial outage)

  2. identified Jun 11, 2026, 02:17 PM UTC

    Status: Identified 🔍 We are currently investigating reports of an issue. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components SAP: East US (Partial outage)

  3. monitoring Jun 11, 2026, 04:40 PM UTC

    Status: Monitoring 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components SAP: East US (Operational)

  4. resolved Jun 11, 2026, 08:11 PM UTC

    Status: Resolved 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components SAP: East US (Operational)

Read the full incident report →

Minor June 10, 2026

Testim issues with testim grid

Detected by Pingoru
Jun 10, 2026, 05:13 PM UTC
Resolved
Jun 10, 2026, 05:13 PM UTC
Duration
—
Affected: US-EAST-1 | GridUS-WEST-2 | Testim
Timeline · 4 updates
  1. investigating Jun 10, 2026, 10:46 AM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue during usage of testim grid. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-WEST-2 | Testim (Degraded performance)

  2. identified Jun 10, 2026, 10:58 AM UTC

    Status: Identified 🔍 We are currently investigating reports of an issue. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-WEST-2 | Testim (Degraded performance)

  3. monitoring Jun 10, 2026, 01:11 PM UTC

    Status: Monitoring 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components US-WEST-2 | Testim (Operational) US-EAST-1 | Grid (Degraded performance)

  4. resolved Jun 10, 2026, 05:13 PM UTC

    Status: Resolved 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components US-EAST-1 | Grid (Operational) US-WEST-2 | Testim (Operational)

Read the full incident report →

Minor June 10, 2026

Tosca for some new tenants created yesterday is not working

Detected by Pingoru
Jun 10, 2026, 10:45 AM UTC
Resolved
Jun 10, 2026, 10:45 AM UTC
Duration
—
Affected: Japan EastCanada CentralAustralia EastEast USWest Europe
Timeline · 4 updates
  1. investigating Jun 02, 2026, 03:17 PM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue with not assigned licence to a new customers. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components West Europe (Degraded performance) East US (Degraded performance)

  2. identified Jun 02, 2026, 03:22 PM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components Canada Central (Degraded performance) West Europe (Degraded performance) East US (Degraded performance) Australia East (Degraded performance) Japan East (Degraded performance)

  3. monitoring Jun 02, 2026, 05:27 PM UTC

    Status: Monitoring 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components Japan East (Operational) Canada Central (Operational) West Europe (Operational) East US (Operational) Australia East (Operational)

  4. resolved Jun 10, 2026, 10:45 AM UTC

    Status: Resolved 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components Canada Central (Operational) West Europe (Operational) East US (Operational) Australia East (Operational) Japan East (Operational)

Read the full incident report →

Minor June 1, 2026

Possible issues with SSO sign-in

Detected by Pingoru
Jun 01, 2026, 03:29 PM UTC
Resolved
Jun 01, 2026, 03:29 PM UTC
Duration
—
Affected: EU-CENTRAL-1 | TestimUS-WEST-2 | Testim
Timeline · 3 updates
  1. investigating Jun 01, 2026, 12:25 PM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue. Some Testim users may have trouble signing in with SSO (single sign-on). The SSO option may not appear on the login page, or sign-in may fail. Not all users are affected. Sign-in with email and password continues to work. We’re looking into an issue with a third-party service provider and working to restore normal SSO sign-in. We appreciate your patience while we resolve this. Affected components US-WEST-2 | Testim (Degraded performance) EU-CENTRAL-1 | Testim (Degraded performance)

  2. monitoring Jun 01, 2026, 01:22 PM UTC

    Status: Monitoring 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components US-WEST-2 | Testim (Operational) EU-CENTRAL-1 | Testim (Operational)

  3. resolved Jun 01, 2026, 03:29 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-WEST-2 | Testim (Operational) EU-CENTRAL-1 | Testim (Operational)

Read the full incident report →

Minor May 29, 2026

Customers may experience slowness in EU region

Detected by Pingoru
May 29, 2026, 08:34 AM UTC
Resolved
May 29, 2026, 08:34 AM UTC
Duration
—
Affected: EU-WEST-1 | Region 6
Timeline · 2 updates
  1. investigating May 26, 2026, 12:50 PM UTC

    Status: Investigating We are currently investigating reports of the slowness. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components EU-WEST-1 | Region 6 (Degraded performance)

  2. resolved May 29, 2026, 08:34 AM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components EU-WEST-1 | Region 6 (Operational)

Read the full incident report →

Minor May 27, 2026

Tosca not working onboarding of new customers

Detected by Pingoru
May 27, 2026, 05:03 AM UTC
Resolved
May 27, 2026, 05:03 AM UTC
Duration
—
Affected: SAP: West Europe
Timeline · 4 updates
  1. investigating May 26, 2026, 10:04 AM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue with onboarding new customers. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components SAP: West Europe (Partial outage)

  2. identified May 26, 2026, 11:08 AM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components SAP: West Europe (Partial outage)

  3. monitoring May 26, 2026, 07:54 PM UTC

    Status: Monitoring 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components SAP: West Europe (Operational)

  4. resolved May 27, 2026, 05:03 AM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components SAP: West Europe (Operational)

Read the full incident report →

Minor May 21, 2026

Customers may experience intermittent latencies in EU region

Detected by Pingoru
May 21, 2026, 05:01 PM UTC
Resolved
May 21, 2026, 05:01 PM UTC
Duration
—
Affected: EU-WEST-1 | Region 6
Timeline · 2 updates
  1. identified May 21, 2026, 03:01 PM UTC

    Status: Identified We are actively working on mitigation steps and implementing fixes to stabilize performance and reduce impact. Users may experience intermittent latency across parts of the platform during this time. We will continue to provide updates as progress is made. Affected components EU-WEST-1 | Region 6 (Degraded performance)

  2. resolved May 21, 2026, 05:01 PM UTC

    Status: Resolved ✅ The performance issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components EU-WEST-1 | Region 6 (Operational)

Read the full incident report →

Minor May 21, 2026

AI Workspace Workflow Execution Issues

Detected by Pingoru
May 21, 2026, 07:43 AM UTC
Resolved
May 21, 2026, 07:43 AM UTC
Duration
—
Affected: AP-SOUTHEAST-2EU-WEST-3US-EAST-1
Timeline · 5 updates
  1. investigating May 11, 2026, 12:45 PM UTC

    Status: Investigating We are currently investigating an issue impacting AI Workspace, where some customers may experience missing API toolsets and failed workflow executions. Our Engineering is actively working on a resolution. Affected components AP-SOUTHEAST-2 (Partial outage) EU-WEST-3 (Partial outage) US-EAST-1 (Partial outage)

  2. monitoring May 11, 2026, 07:05 PM UTC

    Status: Monitoring The fix has been deployed for API toolsets, showing 0 tools in the Toolset page. • Toolsets created from OpenAPI/Swagger URLs recover automatically after the next restart. • Toolsets created by pasted spec content must be manually re-added. • Toolsets created from presets (e.g. Jira, Harness) must be deleted and recreated. How to check if you’re affected Go to the Toolset page and look for API toolsets showing 0 tools. If you need assistance recovering or recreating your toolsets, please contact Support. Affected components AP-SOUTHEAST-2 (Operational) EU-WEST-3 (Operational) US-EAST-1 (Operational)

  3. identified May 12, 2026, 01:39 PM UTC

    Status: Identified We are continuing to investigate an issue affecting API Toolsets. Some customers may see API Toolsets displaying 0 tools in the Toolset page, which can impact workflow execution. Our engineering team is actively working on mitigation and recovery steps. We will provide further updates as more information becomes available. Affected components AP-SOUTHEAST-2 (Partial outage) EU-WEST-3 (Partial outage) US-EAST-1 (Partial outage)

  4. monitoring May 12, 2026, 07:03 PM UTC

    Status: Monitoring We have applied mitigation steps for the API Toolset issue across EU, US, and APAC production environments. Services are operating normally, and we are continuing to monitor closely while validating with impacted customers. Affected components EU-WEST-3 (Operational) US-EAST-1 (Operational) AP-SOUTHEAST-2 (Operational)

  5. resolved May 21, 2026, 07:43 AM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components EU-WEST-3 (Operational) US-EAST-1 (Operational) AP-SOUTHEAST-2 (Operational)

Read the full incident report →

Minor May 20, 2026

TestExecutionAPI degraded performance in us-east-1

Detected by Pingoru
May 20, 2026, 06:04 PM UTC
Resolved
May 20, 2026, 06:04 PM UTC
Duration
—
Affected: US-EAST-1 | Region 1
Timeline · 3 updates
  1. investigating May 20, 2026, 03:54 PM UTC

    Status: Investigating We are currently investigating the slowness of TestExecutionAPI. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-EAST-1 | Region 1 (Degraded performance)

  2. monitoring May 20, 2026, 04:22 PM UTC

    Status: Monitoring We are currently monitoring the performance of TestExecutionAPI. A fix has been implemented, and processing pace has been restored to normal operating speed. Current processing values are back within expected ranges. Affected components US-EAST-1 | Region 1 (Operational)

  3. resolved May 20, 2026, 06:04 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-EAST-1 | Region 1 (Operational)

Read the full incident report →

Minor May 20, 2026

Tosca API Playground outage

Detected by Pingoru
May 20, 2026, 04:22 PM UTC
Resolved
May 20, 2026, 04:22 PM UTC
Duration
—
Affected: SAP: West EuropeJapan EastCanada CentralSAP: EuropeAustralia EastEast USWest EuropeSAP: East US
Timeline · 3 updates
  1. investigating May 20, 2026, 01:50 PM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue with API Playground. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components Japan East (Partial outage) Canada Central (Partial outage) SAP: East US (Partial outage) West Europe (Partial outage) East US (Partial outage) SAP: Europe (Partial outage) SAP: West Europe (Partial outage) Australia East (Partial outage)

  2. identified May 20, 2026, 04:21 PM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components Australia East (Partial outage) Japan East (Partial outage) Canada Central (Partial outage) SAP: East US (Partial outage) West Europe (Partial outage) East US (Partial outage) SAP: Europe (Partial outage) SAP: West Europe (Partial outage)

  3. resolved May 20, 2026, 04:22 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components SAP: Europe (Operational) SAP: West Europe (Operational) Australia East (Operational) Japan East (Operational) Canada Central (Operational) SAP: East US (Operational) West Europe (Operational) East US (Operational)

Read the full incident report →

Minor May 19, 2026

Unavailability of the Sessions in us-east-2

Detected by Pingoru
May 19, 2026, 03:14 PM UTC
Resolved
May 19, 2026, 03:14 PM UTC
Duration
—
Affected: US-EAST-2 | Region 13
Timeline · 3 updates
  1. identified May 19, 2026, 02:53 PM UTC

    Status: Identified Users may have experienced unavailability of the Sessions. Team has identified the issue and applied the fix. We are monitoring the situation. Affected components US-EAST-2 | Region 13 (Partial outage)

  2. monitoring May 19, 2026, 02:59 PM UTC

    Status: Monitoring A fix has been implemented and we are currently monitoring the Sessions to ensure everything is working as expected. Affected components US-EAST-2 | Region 13 (Operational)

  3. resolved May 19, 2026, 03:14 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-EAST-2 | Region 13 (Operational)

Read the full incident report →

Minor May 11, 2026

AI Workspace – Investigating Elevated Latency and Slowness Across Multiple Regions

Detected by Pingoru
May 11, 2026, 12:43 PM UTC
Resolved
May 11, 2026, 12:43 PM UTC
Duration
—
Affected: AP-SOUTHEAST-2US-EAST-1
Timeline · 5 updates
  1. investigating May 06, 2026, 05:21 PM UTC

    Status: Investigating We are currently investigating reports of increased latency and slower response times affecting AI Workspace functionality across multiple regions. Our engineering teams are actively analyzing the issue and working to mitigate the impact Affected components AP-SOUTHEAST-2 (Degraded performance) US-EAST-1 (Degraded performance)

  2. investigating May 06, 2026, 07:37 PM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components AP-SOUTHEAST-2 (Operational) US-EAST-1 (Degraded performance)

  3. identified May 06, 2026, 09:47 PM UTC

    Status: Identified We have implemented mitigation actions to improve performance and reduce latency affecting AI Workspace services. Customers should now experience improved responsiveness across impacted functionality. Our teams continue to actively monitor the platform and investigate the underlying root cause. While service performance has improved, some intermittent degradation may still occur under high load conditions. Affected components AP-SOUTHEAST-2 (Operational) US-EAST-1 (Degraded performance)

  4. monitoring May 07, 2026, 12:37 PM UTC

    Status: Monitoring 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components AP-SOUTHEAST-2 (Operational) US-EAST-1 (Operational)

  5. resolved May 11, 2026, 12:43 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components AP-SOUTHEAST-2 (Operational) US-EAST-1 (Operational)

Read the full incident report →

Minor May 6, 2026

AI Workspace login issue

Detected by Pingoru
May 06, 2026, 01:54 PM UTC
Resolved
May 06, 2026, 01:54 PM UTC
Duration
—
Affected: AP-SOUTHEAST-2EU-WEST-3US-EAST-1
Timeline · 3 updates
  1. investigating May 06, 2026, 10:24 AM UTC

    Status: Investigating We are currently investigating an issue where some customers may be unable to log in to AI Workspace. Our engineering team is actively working on identifying the root cause and restoring full functionality as quickly as possible. Affected components AP-SOUTHEAST-2 (Partial outage) EU-WEST-3 (Partial outage) US-EAST-1 (Partial outage)

  2. monitoring May 06, 2026, 11:07 AM UTC

    Status: Monitoring AI Workspace functionality has been restored following mitigation activities. The service is currently operating normally, and our teams are closely monitoring the environment to ensure stability. Affected components AP-SOUTHEAST-2 (Operational) EU-WEST-3 (Operational) US-EAST-1 (Operational)

  3. resolved May 06, 2026, 01:54 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components AP-SOUTHEAST-2 (Operational) EU-WEST-3 (Operational) US-EAST-1 (Operational)

Read the full incident report →

Minor May 5, 2026

AI Workspace

Detected by Pingoru
May 05, 2026, 09:11 PM UTC
Resolved
May 05, 2026, 09:11 PM UTC
Duration
—
Affected: AP-SOUTHEAST-2US-EAST-1
Timeline · 5 updates
  1. investigating May 04, 2026, 04:35 PM UTC

    Status: Investigating We are currently investigating an issue causing partial data visibility and degraded performance for some customers. There is no indication of data loss at this time. Our team is actively working on mitigation. Affected components AP-SOUTHEAST-2 (Degraded performance) US-EAST-1 (Degraded performance)

  2. investigating May 04, 2026, 06:18 PM UTC

    Status: Investigating 👀 A fix has been implemented. Please log out and log back in to refresh your session. We will continue to monitor the situation closely. Affected components AP-SOUTHEAST-2 (Operational) US-EAST-1 (Operational)

  3. investigating May 04, 2026, 06:20 PM UTC

    Status: Investigating 👀 A fix has been implemented. Please log out and log back in to refresh your session. We will continue to monitor the situation closely. Affected components AP-SOUTHEAST-2 (Operational) US-EAST-1 (Operational)

  4. monitoring May 04, 2026, 06:20 PM UTC

    Status: Monitoring 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components US-EAST-1 (Operational) AP-SOUTHEAST-2 (Operational)

  5. resolved May 05, 2026, 09:11 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components AP-SOUTHEAST-2 (Operational) US-EAST-1 (Operational)

Read the full incident report →

Minor May 5, 2026

qTest Test Log Save Issue – eu-west-1

Detected by Pingoru
May 05, 2026, 08:17 AM UTC
Resolved
May 05, 2026, 08:17 AM UTC
Duration
—
Affected: EU-WEST-1 | Region 6
Timeline · 3 updates
  1. identified May 05, 2026, 07:52 AM UTC

    Status: Identified We are currently investigating an issue in eu-west-1 where, during Test Run execution or Test Log editing in qTest, the “Actual Result” field is not being saved as expected. Affected components EU-WEST-1 | Region 6 (Degraded performance)

  2. monitoring May 05, 2026, 08:00 AM UTC

    Status: Monitoring The issue in eu-west-1 affecting qTest, where the “Actual Result” field was not being saved during Test Run execution or Test Log editing, has now been resolved. All functionality is operating normally. Affected components EU-WEST-1 | Region 6 (Operational)

  3. resolved May 05, 2026, 08:17 AM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components EU-WEST-1 | Region 6 (Operational)

Read the full incident report →

Minor April 30, 2026

[Testim] Signup and Trial Registration Degradation

Detected by Pingoru
Apr 30, 2026, 03:24 PM UTC
Resolved
Apr 30, 2026, 03:24 PM UTC
Duration
—
Affected: US-EAST-1 | GridEU-CENTRAL-1 | TestimUS-WEST-2 | Testim
Timeline · 3 updates
  1. investigating Apr 28, 2026, 01:19 PM UTC

    Status: Investigating We are currently investigating an issue affecting new signup and trial registration flows. Some users may be unable to complete registration at this time. Existing accounts and core Testim functionality are not impacted. Our team is actively working with a third-party provider to restore full service. We will share another update as soon as possble Affected components US-WEST-2 | Testim (Degraded performance) US-EAST-1 | Grid (Degraded performance) EU-CENTRAL-1 | Testim (Degraded performance)

  2. identified Apr 30, 2026, 01:21 PM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components US-WEST-2 | Testim (Degraded performance) US-EAST-1 | Grid (Degraded performance) EU-CENTRAL-1 | Testim (Degraded performance)

  3. resolved Apr 30, 2026, 03:24 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-WEST-2 | Testim (Operational) US-EAST-1 | Grid (Operational) EU-CENTRAL-1 | Testim (Operational)

Read the full incident report →

Minor April 30, 2026

Customers may experience performance issues in multiple regions

Detected by Pingoru
Apr 30, 2026, 12:19 PM UTC
Resolved
Apr 30, 2026, 12:19 PM UTC
Duration
—
Affected: US-EAST-1 | Region 1AP-SOUTHEAST-2 | Region 8US-EAST-2 | Region 13US-WEST-2 | Region 7
Timeline · 3 updates
  1. 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)

  2. 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)

  3. 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)

Read the full incident report →

Minor April 30, 2026

AI WorkSpace - Github webhooks might failing

Detected by Pingoru
Apr 30, 2026, 10:39 AM UTC
Resolved
Apr 30, 2026, 10:39 AM UTC
Duration
—
Affected: AP-SOUTHEAST-2EU-WEST-3US-EAST-1
Timeline · 3 updates
  1. investigating Apr 22, 2026, 06:17 PM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-EAST-1 (Degraded performance) AP-SOUTHEAST-2 (Degraded performance) EU-WEST-3 (Degraded performance)

  2. identified Apr 28, 2026, 06:32 AM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components AP-SOUTHEAST-2 (Degraded performance) EU-WEST-3 (Degraded performance) US-EAST-1 (Degraded performance)

  3. resolved Apr 30, 2026, 10:39 AM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components AP-SOUTHEAST-2 (Operational) EU-WEST-3 (Operational) US-EAST-1 (Operational)

Read the full incident report →

Minor April 30, 2026

Testim Exexution experience degraded

Detected by Pingoru
Apr 30, 2026, 09:51 AM UTC
Resolved
Apr 30, 2026, 09:51 AM UTC
Duration
—
Affected: US-EAST-1 | GridEU-CENTRAL-1 | TestimUS-WEST-2 | Testim
Timeline · 4 updates
  1. investigating Apr 30, 2026, 07:52 AM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-WEST-2 | Testim (Degraded performance) US-EAST-1 | Grid (Degraded performance) EU-CENTRAL-1 | Testim (Degraded performance)

  2. identified Apr 30, 2026, 09:49 AM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components US-WEST-2 | Testim (Degraded performance) US-EAST-1 | Grid (Degraded performance) EU-CENTRAL-1 | Testim (Degraded performance)

  3. identified Apr 30, 2026, 09:49 AM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components US-WEST-2 | Testim (Degraded performance) US-EAST-1 | Grid (Degraded performance) EU-CENTRAL-1 | Testim (Degraded performance)

  4. resolved Apr 30, 2026, 09:51 AM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-WEST-2 | Testim (Operational) US-EAST-1 | Grid (Operational) EU-CENTRAL-1 | Testim (Operational)

Read the full incident report →

Minor April 30, 2026

NeoLoad Performance Issues

Detected by Pingoru
Apr 30, 2026, 07:53 AM UTC
Resolved
Apr 30, 2026, 07:53 AM UTC
Duration
—
Affected: US-EAST-2
Timeline · 5 updates
  1. investigating Apr 29, 2026, 11:02 AM UTC

    Status: Investigating 🔍 We are currently investigating an issue affecting NeoLoad, where users may experience slow loading and error messages Affected components US-EAST-2 (Degraded performance)

  2. investigating Apr 29, 2026, 11:06 AM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-EAST-2 (Degraded performance)

  3. identified Apr 29, 2026, 11:34 AM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components US-EAST-2 (Degraded performance)

  4. monitoring Apr 29, 2026, 01:01 PM UTC

    Status: Monitoring The issue affecting NeoLoad performance has been resolved. Services are now operating normally. We are continuing to closely monitor the system to ensure stability. Affected components US-EAST-2 (Operational)

  5. resolved Apr 30, 2026, 07:53 AM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-EAST-2 (Operational)

Read the full incident report →

Minor April 29, 2026

qTest is unreachable in us-east-1 region

Detected by Pingoru
Apr 29, 2026, 08:20 PM UTC
Resolved
Apr 29, 2026, 08:20 PM UTC
Duration
—
Affected: US-EAST-1 | Region 1
Timeline · 3 updates
  1. investigating Apr 29, 2026, 06:35 PM UTC

    Status: Investigating We are currently investigating an outage affecting qTest in the us-east-1 region. The team is actively working to identify the root cause and will share an update as soon as more information becomes available. Affected components US-EAST-1 | Region 1 (Full outage)

  2. monitoring Apr 29, 2026, 06:56 PM UTC

    Status: Monitoring We have implemented the fix, qTest is back online in us-east-1. Team is closely monitoring the situation. Affected components US-EAST-1 | Region 1 (Operational)

  3. resolved Apr 29, 2026, 08:20 PM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components US-EAST-1 | Region 1 (Operational)

Read the full incident report →

Minor April 28, 2026

Testim temporary grid partial outage

Detected by Pingoru
Apr 28, 2026, 08:00 PM UTC
Resolved
Apr 28, 2026, 08:00 PM UTC
Duration
—
Affected: AP-SOUTHEAST-2EUUS-EAST-2US-EAST-1 | GridUS-EAST-1 | Region 1SAP: West EuropeJapan EastCanada CentralUS-WEST-2EU-WEST-3AP-SOUTHEAST-2 | Region 8US-EAST-2 | Region 13US-WEST-2 | Region 7EU-CENTRAL-1 | TestimSAP: EuropeAustralia EastGlobalEast USUK SouthEU-CENTRAL-1US-WEST-2 | TestimWest EuropeEU-WEST-1 | Region 6SAP: East USUS-EAST-1
Timeline · 2 updates

Read the full incident report →

Minor April 23, 2026

VisionAI authentication issues

Detected by Pingoru
Apr 23, 2026, 10:40 AM UTC
Resolved
Apr 23, 2026, 10:40 AM UTC
Duration
—
Affected: Australia EastEast USUK SouthWest Europe
Timeline · 4 updates
  1. investigating Apr 23, 2026, 09:10 AM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue with authentication. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components Australia East (Partial outage) East US (Partial outage) West Europe (Partial outage) UK South (Partial outage)

  2. identified Apr 23, 2026, 09:10 AM UTC

    Status: Identified 🛠️ We have identified the root cause of the issue and are working on a fix. We’ll continue to share updates as we make progress. Affected components Australia East (Partial outage) East US (Partial outage) West Europe (Partial outage) UK South (Partial outage)

  3. monitoring Apr 23, 2026, 09:28 AM UTC

    Status: Monitoring 👀 A fix has been implemented and we are currently monitoring the system to ensure everything is working as expected. Affected components West Europe (Operational) UK South (Operational) Australia East (Operational) East US (Operational)

  4. resolved Apr 23, 2026, 10:40 AM UTC

    Status: Resolved ✅ The issue has been resolved. All systems are operating normally. Thank you for your patience. Affected components Australia East (Operational) East US (Operational) West Europe (Operational) UK South (Operational)

Read the full incident report →