TestRail Outage History

TestRail is up right now

TestRail had 4 outages in the last 2 years totaling 164h 23m of downtime — averaging 0.2 incidents per month.

There were 4 TestRail outages since March 20, 2026 totaling 164h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://testrail.statuspage.io

Major August 19, 2026

Performance issue impacting access to TestRail

Detected by Pingoru
Aug 19, 2026, 11:32 AM UTC
Resolved
Aug 19, 2026, 02:00 PM UTC
Duration
2h 27m
Affected: TestRail Cloud
Timeline · 3 updates
  1. investigating Aug 19, 2026, 11:32 AM UTC

    We are aware of an issue affecting TestRail where some users may experience slower performance and/or 500 errors. Our team is working to restore full functionality. Updates will follow as soon as we have more to share.

  2. monitoring Aug 19, 2026, 12:34 PM UTC

    A fix has been implemented and we are monitoring the recovery. Some temporary instability may occur during this period as the system recovers. We will update once the system is fully stable.

  3. resolved Aug 19, 2026, 03:38 PM UTC

    The issue affecting TestRail has been resolved and all services are now fully operational. Thank you for your patience.

Read the full incident report →

Minor August 17, 2026

Resolved: DNS Issue Affecting Access to TestRail

Detected by Pingoru
Aug 17, 2026, 03:17 PM UTC
Resolved
Aug 17, 2026, 12:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 17, 2026, 03:17 PM UTC

    We identified a DNS issue that may have prevented some users from accessing TestRail. The issue has been resolved, and all services are now fully operational. We apologize for any inconvenience and thank you for your patience.

Read the full incident report →

Minor August 11, 2026

Performance Degradation Affecting a Subset of Cloud Instances

Detected by Pingoru
Aug 11, 2026, 06:03 PM UTC
Resolved
Aug 14, 2026, 03:39 PM UTC
Duration
2d 21h
Affected: TestRail Cloud
Timeline · 3 updates
  1. identified Aug 11, 2026, 06:03 PM UTC

    We identified a performance issue affecting a subset of TestRail Cloud accounts, resulting in slower page load times for some users. Our team identified the underlying cause and implemented a mitigation that has stabilized performance. We are continuing to closely monitor the environment while we work toward a permanent resolution. We appreciate your patience and understanding as we work to fully resolve the issue.

  2. monitoring Aug 12, 2026, 04:15 PM UTC

    We continue to closely monitor performance for the affected Cloud instances following the mitigation applied earlier. Our team has identified a permanent resolution, which is currently undergoing review and testing. Thank you for your continued patience while we finalize this work.

  3. resolved Aug 14, 2026, 03:39 PM UTC

    The issue affecting a small subset of customers has been resolved and all services are now fully operational. Thank you for your patience.

Read the full incident report →

Minor March 20, 2026

Jira Integration Degradation

Detected by Pingoru
Mar 20, 2026, 02:00 AM UTC
Resolved
Mar 23, 2026, 10:20 PM UTC
Duration
3d 20h
Affected: TestRail Jira Integration (Cloud)
Timeline · 8 updates
  1. investigating Mar 20, 2026, 01:15 PM UTC

    We are currently investigating an issue affecting authentication for the Jira integration. Some users may experience failures when connecting to Jira or syncing data between TestRail and Jira. Our team is actively working to identify the root cause and will provide updates as more information becomes available.

  2. investigating Mar 20, 2026, 03:30 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 20, 2026, 03:31 PM UTC

    We have identified the root cause of the issue affecting authentication for the Jira integration and are actively working to implement a fix. Some users may continue to experience failures when connecting to Jira or syncing data between TestRail and Jira during this time. We will provide further updates as remediation progresses.

  4. identified Mar 20, 2026, 05:56 PM UTC

    We are continuing to implement a fix for the issue. Further updates will be provided as progress continues.

  5. identified Mar 20, 2026, 10:27 PM UTC

    Work to implement a fix is ongoing. During this time, some users may encounter “500 server error” messages when attempting to authenticate with or use the Jira integration. We will share additional updates as they become available.

  6. identified Mar 22, 2026, 12:27 AM UTC

    We are continuing to make progress on implementing the fix. Some customers may still experience issues, including “500 server error” messages when using the Jira integration. We appreciate your patience and will share further updates as they become available.

  7. monitoring Mar 22, 2026, 08:06 PM UTC

    A fix has been implemented for the issue affecting authentication with the Jira integration. We are currently monitoring to ensure the issue is fully resolved. Users will need to reauthenticate with Jira within TestRail for the fix to take effect. After reauthenticating, normal functionality should resume. We will continue to monitor and provide further updates as needed.

  8. resolved Mar 23, 2026, 10:20 PM UTC

    Following the implementation of the fix, we have completed a period of monitoring and have confirmed that the issue affecting authentication with the Jira integration has been fully resolved, with no further errors observed. Users should ensure they have reauthenticated with Jira within TestRail to maintain normal functionality. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →