Testrail 장애 기록

1. 2026년 8월 19일 AM 11:32 UTCinvestigating

   우리는 TestRail에 영향을 미치는 문제의 인식은 일부 사용자가 느린 성능과 / 또는 500 오류를 경험할 수 있습니다. 우리 팀은 전체 기능을 복원하기 위해 노력하고 있습니다. 업데이트는 우리가 공유하는 더 많은 것을 가지고 있기 때문에 곧 따릅니다.

2. 2026년 8월 19일 PM 12:34 UTCmonitoring

   수정이 구현되어 복구를 모니터링하고 있습니다. 일부 임시 불안정은 시스템 복구로이 기간 동안 발생할 수 있습니다. 우리는 일단 체계가 완전히 안정되어 있는 한 번 갱신할 것입니다.

3. 2026년 8월 19일 PM 3:38 UTCresolved

   TestRail에 영향을 미치는 문제는 해결되고 모든 서비스는 이제 완전히 운영됩니다. 감사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 17일 PM 3:17 UTCresolved

   우리는 TestRail에 액세스하여 일부 사용자를 방지 할 수있는 DNS 문제를 발견했습니다. 문제는 해결되었습니다. 모든 서비스는 이제 완전히 운영됩니다. 우리는 어떤 불편을 드려 대단히 감사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 11일 PM 6:03 UTCidentified

   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. 2026년 8월 12일 PM 4:15 UTCmonitoring

   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. 2026년 8월 14일 PM 3:39 UTCresolved

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

1. 2026년 3월 20일 PM 1:15 UTCinvestigating

   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. 2026년 3월 20일 PM 3:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 3월 20일 PM 3:31 UTCidentified

   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. 2026년 3월 20일 PM 5:56 UTCidentified

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

5. 2026년 3월 20일 PM 10:27 UTCidentified

   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. 2026년 3월 22일 AM 12:27 UTCidentified

   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. 2026년 3월 22일 PM 8:06 UTCmonitoring

   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. 2026년 3월 23일 PM 10:20 UTCresolved

   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.

1. 2024년 2월 26일 PM 4:22 UTCinvestigating

   Some customers may be experiencing degraded performance. Our engineers are investigating.

2. 2024년 2월 26일 PM 6:57 UTCidentified

   Our team is actively working to resolve the incident. Customers may see their instances in maintenance mode intermittently, but for no longer than 15 minutes.

3. 2024년 2월 26일 PM 8:19 UTCidentified

   Some customers may experience maintenance windows longer than 15 minutes as our team continues to work to resolve the incident.

4. 2024년 2월 27일 AM 12:10 UTCmonitoring

   The incident has been resolved, and all customers should now have access to their instances. Please note that we have temporarily increased the API rate limit restrictions, and reduced the background task frequency while we monitor the system. We appreciate your patience during this time, and are committed to maintaining service stability.

5. 2024년 2월 27일 AM 9:02 UTCmonitoring

   Some customers are experiencing degraded performance. Our engineers are investigating.

6. 2024년 2월 27일 PM 3:50 UTCmonitoring

   We're pleased to report significant performance improvements across our platform, with decreased error rates and API rate limits restored to their normal levels. Our team continues to closely monitor the system to ensure ongoing stability and reliability. Thank you for your patience and support.

7. 2024년 2월 27일 PM 8:02 UTCresolved

   This incident has been resolved.

1. 2024년 2월 19일 AM 10:48 UTCinvestigating

   Some customers may be experiencing degraded performance. Our engineers are investigating.

2. 2024년 2월 19일 PM 12:34 UTCidentified

   Our engineers have identified the potential source and implemented a fix.

3. 2024년 2월 19일 PM 1:44 UTCresolved

   This incident has been resolved.

1. 2024년 2월 15일 PM 3:32 UTCmonitoring

   We identified degraded performance that may affect some customers in connection with the 14-Feb partial outage. Our team is actively investigating to ensure a complete resolution.

2. 2024년 2월 16일 PM 3:53 UTCmonitoring

   We're continuing to monitor for any further issues while the team is working to a full resolution.

3. 2024년 2월 18일 PM 11:48 UTCresolved

   We successfully resolved the issue, and normal service has been restored.

1. 2024년 2월 14일 AM 9:14 UTCidentified

   We're currently experiencing a partial Cloud outage which may result in error messages relating to failing API calls or attachment related nodes. We're working on the issue right now and expect to have a resolution shortly.

2. 2024년 2월 14일 AM 10:59 UTCmonitoring

   Customers should be seeing improvements. We will continue to monitor whilst services return to normal.

3. 2024년 2월 14일 PM 12:30 UTCmonitoring

   We are continuing to monitor this issue.

4. 2024년 2월 14일 PM 6:08 UTCmonitoring

   Monitoring continues while the rate of errors continues to reduce sharply.

5. 2024년 2월 15일 AM 8:35 UTCresolved

   The incident has been resolved. We are continuing to monitor for errors.

1. 2023년 10월 12일 PM 5:20 UTCinvestigating

   The TestRail Cloud Attachments service is currently experiencing performance issues affecting a subset of attachments functionality for a small number of TestRail Cloud users. Our DevOps team is deploying a fix and we expect to resolve this matter promptly.

2. 2023년 10월 12일 PM 5:20 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2023년 10월 13일 AM 8:24 UTCidentified

   We're still working to fix this issue as fast as we can. Thanks for your patience while we do so. We'll share updates as progress is made.

4. 2023년 10월 14일 AM 8:45 UTCidentified

   We are continuing to work on a fix for this issue which is affecting a small number of customers. Thanks for your patience. Our team is working hard to complete this activity as quickly as possible and we appreciate your bearing with us while we do so.

5. 2023년 10월 16일 AM 7:08 UTCmonitoring

   Our team is stabilising our hosted infrastructure after applying the necessary fixes. We are continuing to monitor the situation closely.

6. 2023년 10월 16일 PM 9:24 UTCresolved

   Our DevOps team has applied a fix for this issue and after a period of monitoring, has determined that users should no longer be experiencing issues related to the TestRail attachments service. We appreciate your patience while we dealt with this matter. If you're still experiencing errors that result in a "Call to a member function prepare()" message, please reach out to our support team and we'll be happy to assist.

1. 2023년 6월 1일 AM 7:35 UTCinvestigating

   One of our databases is not responding correctly and as a result, TestRail instances reliant on it are currently in maintenance mode. Our DevOps team is investigating the problem.

2. 2023년 6월 1일 AM 8:28 UTCidentified

   The cause of the database issue has been identified and our engineers are working to solve the problem. In the meantime, we are also building a new database from a backup with a view towards switching affected customers to the new database.

3. 2023년 6월 1일 AM 9:30 UTCmonitoring

   The database has been recovered and all affected TestRail cloud instances should now be back online. We are continuing to monitor the database for any further issues.

4. 2023년 6월 1일 AM 11:43 UTCresolved

   All systems are operational.

1. 2022년 9월 7일 PM 12:08 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 9월 7일 PM 1:17 UTCresolved

   The issue has been identified and a fix implemented. We will be continuing to monitor the situation.

1. 2022년 9월 5일 AM 8:53 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 9월 5일 AM 9:28 UTCidentified

   We have identified the cause of this issue and we are currently in the process of implementing a fix.

3. 2022년 9월 5일 PM 12:57 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2022년 9월 5일 PM 2:03 UTCresolved

   This incident has been resolved.

1. 2022년 8월 17일 PM 12:22 UTCinvestigating

   Some customers are experiencing gateway errors, e.g. '502 Bad Gateway', '504 Gateway Time-out', or '403-Access Denied' when attempting to access their TestRail cloud instance. We are currently investigating this issue and will provide further updates shortly.

2. 2022년 8월 17일 PM 4:46 UTCinvestigating

   We are continuing to investigate this issue.

3. 2022년 8월 17일 PM 4:46 UTCidentified

   We have identified the issue in which some customers have experienced gateway errors (502 - Bad Gateway, 504 - Gateway Time-out, 403 - Access Denied) when attempting to access their TestRail Cloud instance. We have resolved the issue for several of our customer instances and expect to resolve the remaining instances shortly.

4. 2022년 8월 17일 PM 5:24 UTCmonitoring

   We have fixed the issue encountered by some customers earlier today in regards to Gateway Access issues. We are monitoring the situation.

5. 2022년 8월 18일 PM 5:58 UTCresolved

   This incident has been resolved.

1. 2022년 6월 14일 PM 12:58 UTCinvestigating

   Some customers are experiencing slower than expected TestRail performance. We are currently investigating this issue.

2. 2022년 6월 14일 PM 2:19 UTCmonitoring

   We have identified the cause of the instability and implemented a fix which we are currently monitoring.

3. 2022년 6월 22일 PM 12:15 UTCresolved

   This incident has been resolved.

1. 2022년 5월 4일 AM 7:18 UTCinvestigating

   Some customers are experiencing an error when attempting to add test results. We are currently investigating the cause of this issue and will provide an update shortly.

2. 2022년 5월 4일 AM 8:24 UTCinvestigating

   We are continuing to investigate this issue and will provide further updates shortly. In the meantime, users are able to workaround the problem by using the "Pass & Next" button to add a result instead of the "Add Result" button.

3. 2022년 5월 4일 AM 9:24 UTCinvestigating

   Our team has identified the issue and implemented a fix. All cloud customers will receive the fix shortly.

4. 2022년 5월 4일 AM 10:46 UTCmonitoring

   We have deployed the fix to all customers and are monitoring for any further issues.

5. 2022년 5월 4일 PM 2:35 UTCresolved

   This incident has been resolved.

1. 2022년 3월 8일 PM 2:38 UTCinvestigating

   Some customers are experiencing gateway errors, e.g. '502 Bad Gateway' or '504 Gateway Time-out', when attempting to access their TestRail cloud instance. We are currently investigating this issue and will provide further updates shortly.

2. 2022년 3월 8일 PM 4:57 UTCresolved

   This incident has been resolved.

1. 2022년 3월 7일 PM 12:58 UTCinvestigating

   Some customers are experiencing gateway errors, e.g. '502 Bad Gateway' or '504 Gateway Time-out', when attempting to access their TestRail cloud instance. We are currently investigating this issue and will provide further updates shortly.

2. 2022년 3월 7일 PM 2:00 UTCmonitoring

   Earlier today we had some further reports of further 504 and 502 gateway errors affecting a small number of customers. We've identified the cause of the errors and implemented a fix. Service to TestRail Cloud has been fully restored and all instances are showing as online and operational. We will continue to monitor closely to ensure there are no other issues. If you are still receiving any 502 or 504 gateway errors, please email us at [email protected] so that we can take a closer look at your specific instance.

3. 2022년 3월 8일 AM 10:59 UTCresolved

   This incident has been resolved.

1. 2022년 3월 7일 AM 9:08 UTCinvestigating

   TestRail Cloud is currently experiencing issues. We know this is frustrating and we’re working to resolve this as soon as possible. We have escalated this to our engineering team, and will provide an update as soon as more information becomes available.

2. 2022년 3월 7일 AM 9:26 UTCmonitoring

   We have identified and resolved the issue. All instances are operational, however we are continuing to closely monitor the situation.

3. 2022년 3월 7일 AM 11:05 UTCresolved

   This incident has been resolved.

1. 2022년 3월 2일 AM 1:44 UTCmonitoring

   TestRail Cloud is fully operational, but we are continuing to monitor and investigate reports of intermittent 504 and 502 gateway errors, including for the TestRail API, as well as some other issues related to timeouts. We will post an update as soon as we have more information. If you or a teammate is experiencing any issues, please notify our Support team at [email protected] so we can help triage.

2. 2022년 3월 2일 AM 9:08 UTCmonitoring

   Earlier today we had some further reports of further 504 and 502 gateway errors affecting a small number of customers. We've identified the cause of the errors and implemented a fix. Service to TestRail Cloud has been fully restored and all instances are showing as online and operational. We will continue to monitor closely to ensure there are no other issues. If you are still receiving any 502 or 504 gateway errors, please email us at [email protected] so that we can take a closer look at your specific instance.

3. 2022년 3월 3일 AM 11:00 UTCresolved

   This incident has been resolved.

1. 2022년 3월 1일 AM 9:11 UTCinvestigating

   Some customers are experiencing gateway errors, e.g. '502 Bad Gateway' or '504 Gateway Time-out', when attempting to access their TestRail cloud instance. We are currently investigating this issue and will provide further updates shortly.

2. 2022년 3월 1일 AM 11:23 UTCinvestigating

   We are continuing to investigate this issue. We do not have an ETA for resolution at the present time, but expect to provide one shortly.

3. 2022년 3월 1일 PM 1:39 UTCinvestigating

   We are continuing to investigate this issue.

4. 2022년 3월 1일 PM 6:35 UTCinvestigating

   TestRail Cloud continues to experience issues with 502 or 504 gateway errors. We know this is frustrating and we’re working to resolve this as soon as possible. We have escalated this to our engineering team, and will provide an update as soon as more information becomes available.

5. 2022년 3월 1일 PM 8:09 UTCmonitoring

   We've identified the cause of the gateway errors and implemented a fix. Service to TestRail Cloud has been fully restored and all instances are showing as online and operational. We will continue to monitor closely to ensure there are no other issues. If you are still receiving any 502 or 504 gateway errors, please email us at [email protected] so that we can take a closer look at your specific instance.

6. 2022년 3월 1일 PM 8:10 UTCresolved

   This incident has been resolved.