TestRail had 3 outages in the last 2 years totaling 161h 56m of downtime — averaging 0.1 incidents per month.
There were 3 TestRail outages since March 20, 2026 totaling 161h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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.
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.
The issue affecting a small subset of customers has been resolved and all services are now fully operational. Thank you for your patience.
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.
We are continuing to investigate this issue.
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.
We are continuing to implement a fix for the issue. Further updates will be provided as progress continues.
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.
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.
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.
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.