Tricentis Outage History

Tricentis is up right now

There were 33 Tricentis outages since February 3, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tricentis.com

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
  1. identified Apr 28, 2026, 05:30 PM UTC

    Status: Identified 🛠️ We have identified an issue with the grid, our provider is working on a fix. We’ll continue to share updates as we make progress. Affected components SAP: Europe (Operational) West Europe (Operational) Global (Operational) Japan East (Operational) US-EAST-1 (Operational) EU-WEST-1 | Region 6 (Operational) Australia East (Operational) EU-CENTRAL-1 (Operational) EU-WEST-3 (Operational) Australia East (Operational) US-WEST-2 | Region 7 (Operational) SAP: East US (Operational) US-EAST-2 (Operational) US-WEST-2 | Testim (Operational) US-EAST-1 | Region 1 (Operational) UK South (Operational) EU-CENTRAL-1 | Testim (Operational) West Europe (Operational) East US (Operational) US-WEST-2 (Operational) Canada Central (Operational) East US (Operational) US-EAST-1 | Grid (Partial outage) US-EAST-2 | Region 13 (Operational) EU (Operational) AP-SOUTHEAST-2 | Region 8 (Operational) Global (Operational) US-EAST-1 (Operational) SAP: West Europe (Operational) AP-SOUTHEAST-2 (Operational)

  2. resolved Apr 28, 2026, 08:00 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) Japan East (Operational) Canada Central (Operational) East US (Operational) West Europe (Operational) East US (Operational) US-EAST-1 | Region 1 (Operational) Global (Operational) AP-SOUTHEAST-2 (Operational) EU (Operational) Australia East (Operational) US-WEST-2 | Region 7 (Operational) West Europe (Operational) US-EAST-1 (Operational) US-EAST-2 (Operational) Global (Operational) Australia East (Operational) US-EAST-1 (Operational) SAP: Europe (Operational) AP-SOUTHEAST-2 | Region 8 (Operational) UK South (Operational) EU-CENTRAL-1 | Testim (Operational) US-WEST-2 | Testim (Operational) SAP: West Europe (Operational) US-EAST-1 | Grid (Operational) US-WEST-2 (Operational) EU-WEST-3 (Operational) SAP: East US (Operational) EU-WEST-1 | Region 6 (Operational) EU-CENTRAL-1 (Operational)

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 →

Minor April 22, 2026

Customers experience issues with Trial creation in us-east-2

Detected by Pingoru
Apr 22, 2026, 04:11 PM UTC
Resolved
Apr 22, 2026, 04:11 PM UTC
Duration
—
Affected: US-EAST-2 | Region 13
Timeline · 2 updates
  1. investigating Apr 22, 2026, 01:50 PM UTC

    Status: Investigating We are currently investigating reports of an issue during Trial creation in us-east-2. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-EAST-2 | Region 13 (Degraded performance)

  2. resolved Apr 22, 2026, 04:11 PM UTC

    Status: Resolved The issue has been resolved, customers are able to request the Trial versions. Affected components US-EAST-2 | Region 13 (Operational)

Read the full incident report →

Minor April 22, 2026

Testim Slack Notification Degradation

Detected by Pingoru
Apr 22, 2026, 02:32 PM UTC
Resolved
Apr 22, 2026, 02:32 PM UTC
Duration
—
Affected: EU-CENTRAL-1 | TestimUS-WEST-2 | Testim
Timeline · 3 updates
  1. investigating Apr 21, 2026, 09:36 AM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue with slack integration. 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) EU-CENTRAL-1 | Testim (Degraded performance)

  2. monitoring Apr 22, 2026, 07:47 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 US-WEST-2 | Testim (Degraded performance) EU-CENTRAL-1 | Testim (Degraded performance)

  3. resolved Apr 22, 2026, 02:32 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 April 18, 2026

qTest US-WEST-2 slowness

Detected by Pingoru
Apr 18, 2026, 07:55 AM UTC
Resolved
Apr 18, 2026, 07:55 AM UTC
Duration
—
Affected: US-WEST-2 | Region 7
Timeline · 4 updates
  1. investigating Apr 17, 2026, 12:38 PM UTC

    Status: Investigating 🔍 We are currently investigating reports of qTest slowness for incoming requests in the Us-West-2 region. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-WEST-2 | Region 7 (Degraded performance)

  2. investigating Apr 17, 2026, 03:05 PM UTC

    Status: Investigating The response time for the UI is recovered but investigation of performance slowness for regular api endpoints is still ongoing. Affected components US-WEST-2 | Region 7 (Degraded performance)

  3. monitoring Apr 17, 2026, 06:16 PM UTC

    Status: Monitoring Service has been restored in the US-West-2 region and is operating normally. We will continue to monitor system performance closely while the team investigates the root cause in the background. Affected components US-WEST-2 | Region 7 (Operational)

  4. resolved Apr 18, 2026, 07:55 AM 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)

Read the full incident report →

Minor April 17, 2026

AI Workspace – Assisted Agent Creation Issue

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

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

  2. identified Apr 10, 2026, 12:28 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. The issue is caused by too many AI Workspace Tools, as a short-term workaround, please remove unnecessary or unused tools. Tricentis AI team is working on long-term solution how to keep large number of tools in the AI Workspace. Affected components AP-SOUTHEAST-2 (Degraded performance) EU-WEST-3 (Degraded performance) US-EAST-1 (Degraded performance)

  3. resolved Apr 17, 2026, 06:45 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 April 17, 2026

Testim Support Chat Degradation

Detected by Pingoru
Apr 17, 2026, 07:32 AM UTC
Resolved
Apr 17, 2026, 07:32 AM UTC
Duration
—
Affected: US-EAST-1 | GridEU-CENTRAL-1 | TestimUS-WEST-2 | Testim
Timeline · 2 updates
  1. investigating Apr 15, 2026, 08:37 AM UTC

    Status: Investigating We are aware of an issue affecting the Testim in-app support chat. Users may experience errors when using the support assistant or coding assistant features. The root cause has been identified as a deprecated AI model in our backend, and a fix is being deployed. We will provide updates as the resolution progresses. Affected components US-WEST-2 | Testim (Degraded performance) US-EAST-1 | Grid (Degraded performance) EU-CENTRAL-1 | Testim (Degraded performance)

  2. resolved Apr 17, 2026, 07:32 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 16, 2026

Customer may experience an issues during Trial creation in EU region.

Detected by Pingoru
Apr 16, 2026, 05:43 PM UTC
Resolved
Apr 16, 2026, 05:43 PM UTC
Duration
—
Affected: EU-WEST-1 | Region 6
Timeline · 4 updates
  1. investigating Apr 16, 2026, 01:13 PM UTC

    Status: Investigating We are currently investigating reports of an issue with qTest Trial creation in EU region. 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. identified Apr 16, 2026, 01:50 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 EU-WEST-1 | Region 6 (Degraded performance)

  3. monitoring Apr 16, 2026, 05:24 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 EU-WEST-1 | Region 6 (Operational)

  4. resolved Apr 16, 2026, 05:43 PM UTC

    Status: Resolved The issue affecting qTest Trial creation in the EU region has been resolved. Customers can now proceed with creating new trials. If needed, they may also recreate their trial or contact Customer Support for further assistance. Affected components EU-WEST-1 | Region 6 (Operational)

Read the full incident report →

Minor April 8, 2026

Jira Synchronization Delays us-east-1

Detected by Pingoru
Apr 08, 2026, 06:40 PM UTC
Resolved
Apr 08, 2026, 06:40 PM UTC
Duration
—
Affected: US-EAST-1 | Region 1
Timeline · 3 updates
  1. identified Apr 08, 2026, 12:07 PM UTC

    Status: Identified We are currently experiencing delays in Jira synchronization for some customers in us-east-1 region. Our team is actively working to resolve the issue and restore normal processing times. We will continue to provide updates as progress is made. Affected components US-EAST-1 | Region 1 (Degraded performance)

  2. monitoring Apr 08, 2026, 04:34 PM UTC

    Status: Monitoring The issue causing delays in Jira synchronization has been resolved. Synchronization is now operating as expected. Our team continues to monitor the system closely to ensure ongoing stability. Thank you for your patience. Affected components US-EAST-1 | Region 1 (Operational)

  3. resolved Apr 08, 2026, 06:40 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 March 30, 2026

Increase of 5xx response codes in eu-west-1

Detected by Pingoru
Mar 30, 2026, 12:17 PM UTC
Resolved
Mar 30, 2026, 12:17 PM UTC
Duration
—
Affected: EU-WEST-1 | Region 6
Timeline · 3 updates
  1. investigating Mar 30, 2026, 11:13 AM UTC

    Status: Investigating We are currently investigating increased 5xx response codes in eu-west-1. 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. monitoring Mar 30, 2026, 11:47 AM UTC

    Status: Monitoring We have identified the root cause of the increased 5xx responses in eu-west-1 and applied a fix. The system is now stable, and we are closely monitoring the situation to ensure continued normal operation. Affected components EU-WEST-1 | Region 6 (Operational)

  3. resolved Mar 30, 2026, 12:17 PM 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 March 25, 2026

Tosca - reporting service degradation

Detected by Pingoru
Mar 25, 2026, 08:04 PM UTC
Resolved
Mar 25, 2026, 08:04 PM UTC
Duration
—
Affected: SAP: West EuropeJapan EastCanada CentralSAP: EuropeAustralia EastEast USWest EuropeSAP: East US
Timeline · 3 updates
  1. investigating Mar 25, 2026, 09:06 AM UTC

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

  2. monitoring Mar 25, 2026, 03:49 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 (Degraded performance) Australia East (Degraded performance) Japan East (Degraded performance) Canada Central (Degraded performance) SAP: East US (Degraded performance) West Europe (Degraded performance) East US (Degraded performance) SAP: Europe (Degraded performance)

  3. resolved Mar 25, 2026, 08:04 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 March 25, 2026

Project Name Visibility Issue

Detected by Pingoru
Mar 25, 2026, 03:09 PM UTC
Resolved
Mar 25, 2026, 03:09 PM UTC
Duration
—
Affected: EU-WEST-1 | Region 6
Timeline · 4 updates
  1. investigating Mar 25, 2026, 01:49 PM UTC

    Status: Investigating We are currently investigating an issue where the selected project name displayed in the top-left corner of the qTest SaaS interface may be difficult or impossible to read. This issue is affecting the EU-WEST-1 region. Further updates will be provided as more information becomes available. Affected components EU-WEST-1 | Region 6 (Degraded performance)

  2. identified Mar 25, 2026, 02:06 PM UTC

    Status: Identified We have identified the issue where the selected project name displayed in the top-left corner of the qTest SaaS interface may be difficult or impossible to read. A fix is currently being applied. This issue affects the EU-WEST-1 region. We will provide further updates as progress continues. Affected components EU-WEST-1 | Region 6 (Degraded performance)

  3. monitoring Mar 25, 2026, 02:39 PM UTC

    Status: Monitoring We have identified and resolved the issue where the selected project name displayed in the top-left corner of the qTest SaaS interface was difficult or impossible to read. The fix has been applied, and the system is currently operating as expected. This issue affected the EU-WEST-1 region. Our team is continuing to monitor the situation to ensure ongoing stability. Affected components EU-WEST-1 | Region 6 (Operational)

  4. resolved Mar 25, 2026, 03:09 PM 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 March 24, 2026

Testim - Service Degradation

Detected by Pingoru
Mar 24, 2026, 01:24 PM UTC
Resolved
Mar 24, 2026, 01:24 PM UTC
Duration
—
Affected: US-WEST-2 | Testim
Timeline · 4 updates
  1. investigating Mar 24, 2026, 10:55 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)

  2. identified Mar 24, 2026, 12:00 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)

  3. monitoring Mar 24, 2026, 12:00 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 (Degraded performance)

  4. resolved Mar 24, 2026, 01: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)

Read the full incident report →

Minor March 23, 2026

Custom fields shows "no data" in us-west-2

Detected by Pingoru
Mar 23, 2026, 08:31 PM UTC
Resolved
Mar 23, 2026, 08:31 PM UTC
Duration
—
Affected: US-WEST-2 | Region 7
Timeline · 3 updates
  1. investigating Mar 23, 2026, 05:32 PM UTC

    Status: Investigating We are currently investigating reports of an issue of missing data in custom fields. Our team is looking into the cause and will provide an update as soon as we have more information. Affected components US-WEST-2 | Region 7 (Degraded performance)

  2. identified Mar 23, 2026, 06:34 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 | Region 7 (Degraded performance)

  3. resolved Mar 23, 2026, 08:31 PM UTC

    Status: Resolved We have identified and reverted the changes that led to missing data in custom fields. The issue impacted a single customer and has been mitigated. Affected components US-WEST-2 | Region 7 (Operational)

Read the full incident report →

Minor March 13, 2026

Neload web not showing performance metrics or run result

Detected by Pingoru
Mar 13, 2026, 03:17 PM UTC
Resolved
Mar 13, 2026, 03:17 PM UTC
Duration
—
Affected: EUUS-EAST-2
Timeline · 3 updates
  1. investigating Mar 11, 2026, 10:12 PM UTC

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

  2. monitoring Mar 11, 2026, 10:21 PM UTC

    Status: Monitoring A fix has been deployed and we are monitoring the system to confirm full recovery. Performance metrics and run results for runs executed during the incident window may be permanently unavailable. Affected components EU (Operational) US-EAST-2 (Operational)

  3. resolved Mar 13, 2026, 03:17 PM UTC

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

Read the full incident report →

Minor March 13, 2026

Tosca - partial outage in SAP east us region

Detected by Pingoru
Mar 13, 2026, 03:12 PM UTC
Resolved
Mar 13, 2026, 03:12 PM UTC
Duration
—
Affected: SAP: East US
Timeline · 3 updates
  1. investigating Mar 13, 2026, 10:36 AM UTC

    Status: Investigating 🔍 We are currently investigating reports of an issue where some functionality may not work as expected. 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. monitoring Mar 13, 2026, 12: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: East US (Operational)

  3. resolved Mar 13, 2026, 03:12 PM UTC

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

Read the full incident report →

Minor March 12, 2026

Delayed qTest-Jira Integration in eu-west-1

Detected by Pingoru
Mar 12, 2026, 04:12 PM UTC
Resolved
Mar 12, 2026, 04:12 PM UTC
Duration
—
Affected: EU-WEST-1 | Region 6
Timeline · 3 updates
  1. investigating Mar 12, 2026, 02:47 PM UTC

    Status: Investigating We are currently investigating the delay between qTest and Jira synchronization in eu-west-1 region. The team is working to identify the root cause and will provide an update as soon as more information is available. Affected components EU-WEST-1 | Region 6 (Degraded performance)

  2. monitoring Mar 12, 2026, 03:40 PM UTC

    Status: Monitoring The root cause has been addressed and corrective changes have been implemented. The qTest–Jira integration is now stable, with the team continuing close monitoring. Affected components EU-WEST-1 | Region 6 (Operational)

  3. resolved Mar 12, 2026, 04:12 PM 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 March 3, 2026

qTest Manager Unavailable in us-east-1

Detected by Pingoru
Mar 03, 2026, 11:30 AM UTC
Resolved
Mar 03, 2026, 11:30 AM UTC
Duration
—
Affected: US-EAST-1 | Region 1
Timeline · 2 updates
  1. monitoring Mar 03, 2026, 06:11 AM UTC

    Status: Monitoring qTest Manager in us-east-1 is unavailable due to Kubernetes pods failing to start after a misconfigured deployment. The service was restored at ~06:47 UTC and is now in monitoring. Affected components US-EAST-1 | Region 1 (Degraded performance)

  2. resolved Mar 03, 2026, 11:30 AM 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 February 25, 2026

qTest in eu-west-1 experiencing issues with creating test cases

Detected by Pingoru
Feb 25, 2026, 04:52 PM UTC
Resolved
Feb 25, 2026, 04:52 PM UTC
Duration
—
Affected: EU-WEST-1 | Region 6
Timeline · 3 updates
  1. identified Feb 25, 2026, 12:18 PM UTC

    Status: Identified We have identified the issue preventing customers from creating test cases. Our engineering team is actively working to implement mitigation and restore full functionality as quickly as possible. Affected components EU-WEST-1 | Region 6 (Partial outage)

  2. monitoring Feb 25, 2026, 01:10 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 EU-WEST-1 | Region 6 (Partial outage)

  3. resolved Feb 25, 2026, 04:52 PM 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 →

Looking to track Tricentis downtime and outages?

Pingoru polls Tricentis's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Tricentis reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Tricentis alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Tricentis for free

5 free monitors · No credit card required