Historique des pannes de Testrail

1. 22 octobre 2026 à 23:06 UTCinvestigating

   L'intégration TestRail Test Management pour Jira est actuellement indisponible, nous travaillons à résoudre le problème le plus rapidement possible

2. 22 octobre 2026 à 23:06 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 23 octobre 2026 à 00:19 UTCidentified

   Nous avons identifié la cause fondamentale de ce problème et nous travaillons à la mise en œuvre d'une solution.

4. 23 octobre 2026 à 00:40 UTCresolved

   Un correctif a été mis en place et nous surveillons activement nos systèmes.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 19 août 2026 à 11:32 UTCinvestigating

   Nous sommes conscients d'un problème affectant TestRail où certains utilisateurs peuvent éprouver des performances plus lentes et/ou 500 erreurs. Notre équipe travaille à restaurer toutes les fonctionnalités. Les mises à jour suivront dès que nous aurons plus à partager.

2. 19 août 2026 à 12:34 UTCmonitoring

   Un correctif a été mis en place et nous surveillons la reprise. Une certaine instabilité temporaire peut survenir pendant cette période à mesure que le système se rétablit. Nous mettrons à jour une fois le système pleinement stable.

3. 19 août 2026 à 15:38 UTCresolved

   La question concernant TestRail a été résolue et tous les services sont maintenant pleinement opérationnels. Merci de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 17 août 2026 à 15:17 UTCresolved

   Nous avons identifié un problème DNS qui pourrait avoir empêché certains utilisateurs d'accéder à TestRail. La question a été réglée et tous les services sont maintenant pleinement opérationnels. Nous nous excusons de tout désagrément et vous remercions de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 11 août 2026 à 18:03 UTCidentified

   Nous avons identifié un problème de performance affectant un sous-ensemble de comptes TestRail Cloud, ce qui a entraîné un temps de chargement plus lent pour certains utilisateurs. Notre équipe a identifié la cause sous-jacente et mis en oeuvre une atténuation qui a stabilisé le rendement. Nous continuons de surveiller de près l'environnement pendant que nous travaillons à une résolution permanente. Nous apprécions votre patience et votre compréhension dans nos efforts pour résoudre pleinement la question.

2. 12 août 2026 à 16:15 UTCmonitoring

   Nous continuons de surveiller de près les performances pour les cas de Cloud touchés après l'atténuation appliquée précédemment. Notre équipe a identifié une résolution permanente, qui fait actuellement l'objet d'un examen et d'essais. Merci de votre patience pendant que nous terminons ce travail.

3. 14 août 2026 à 15:39 UTCresolved

   Le problème touchant un petit sous-ensemble de clients a été résolu et tous les services sont maintenant pleinement opérationnels. Merci de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 20 mars 2026 à 13: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. 20 mars 2026 à 15:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 mars 2026 à 15: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. 20 mars 2026 à 17:56 UTCidentified

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

5. 20 mars 2026 à 22: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. 22 mars 2026 à 00: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. 22 mars 2026 à 20: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. 23 mars 2026 à 22: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. 26 février 2024 à 16:22 UTCinvestigating

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

2. 26 février 2024 à 18: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. 26 février 2024 à 20:19 UTCidentified

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

4. 27 février 2024 à 00: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. 27 février 2024 à 09:02 UTCmonitoring

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

6. 27 février 2024 à 15: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. 27 février 2024 à 20:02 UTCresolved

   This incident has been resolved.

1. 19 février 2024 à 10:48 UTCinvestigating

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

2. 19 février 2024 à 12:34 UTCidentified

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

3. 19 février 2024 à 13:44 UTCresolved

   This incident has been resolved.

1. 15 février 2024 à 15: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. 16 février 2024 à 15:53 UTCmonitoring

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

3. 18 février 2024 à 23:48 UTCresolved

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

1. 14 février 2024 à 09: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. 14 février 2024 à 10:59 UTCmonitoring

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

3. 14 février 2024 à 12:30 UTCmonitoring

   We are continuing to monitor this issue.

4. 14 février 2024 à 18:08 UTCmonitoring

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

5. 15 février 2024 à 08:35 UTCresolved

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

1. 12 octobre 2023 à 17: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. 12 octobre 2023 à 17:20 UTCidentified

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

3. 13 octobre 2023 à 08: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. 14 octobre 2023 à 08: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. 16 octobre 2023 à 07:08 UTCmonitoring

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

6. 16 octobre 2023 à 21: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. 1 juin 2023 à 07: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. 1 juin 2023 à 08: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. 1 juin 2023 à 09: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. 1 juin 2023 à 11:43 UTCresolved

   All systems are operational.

1. 7 septembre 2022 à 12:08 UTCinvestigating

   We are currently investigating this issue.

2. 7 septembre 2022 à 13:17 UTCresolved

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

1. 5 septembre 2022 à 08:53 UTCinvestigating

   We are currently investigating this issue.

2. 5 septembre 2022 à 09:28 UTCidentified

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

3. 5 septembre 2022 à 12:57 UTCmonitoring

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

4. 5 septembre 2022 à 14:03 UTCresolved

   This incident has been resolved.

1. 17 août 2022 à 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. 17 août 2022 à 16:46 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 août 2022 à 16: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. 17 août 2022 à 17: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. 18 août 2022 à 17:58 UTCresolved

   This incident has been resolved.

1. 14 juin 2022 à 12:58 UTCinvestigating

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

2. 14 juin 2022 à 14:19 UTCmonitoring

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

3. 22 juin 2022 à 12:15 UTCresolved

   This incident has been resolved.

1. 4 mai 2022 à 07: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. 4 mai 2022 à 08: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. 4 mai 2022 à 09:24 UTCinvestigating

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

4. 4 mai 2022 à 10:46 UTCmonitoring

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

5. 4 mai 2022 à 14:35 UTCresolved

   This incident has been resolved.

1. 8 mars 2022 à 14: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. 8 mars 2022 à 16:57 UTCresolved

   This incident has been resolved.

1. 7 mars 2022 à 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. 7 mars 2022 à 14: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. 8 mars 2022 à 10:59 UTCresolved

   This incident has been resolved.

1. 7 mars 2022 à 09: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. 7 mars 2022 à 09:26 UTCmonitoring

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

3. 7 mars 2022 à 11:05 UTCresolved

   This incident has been resolved.

1. 2 mars 2022 à 01: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. 2 mars 2022 à 09: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. 3 mars 2022 à 11:00 UTCresolved

   This incident has been resolved.