Historial de interrupciones de Testrail

1. 19 de agosto de 2026 a las 11:32 UTCinvestigating

   Somos conscientes de un problema que afecta a TestRail donde algunos usuarios pueden experimentar un rendimiento más lento y/o 500 errores. Nuestro equipo está trabajando para restaurar la funcionalidad completa. Las actualizaciones seguirán tan pronto como tengamos más que compartir.

2. 19 de agosto de 2026 a las 12:34 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando la recuperación. Algunas inestabilidades temporales pueden ocurrir durante este período mientras el sistema se recupera. Actualizaremos una vez que el sistema esté completamente estable.

3. 19 de agosto de 2026 a las 15:38 UTCresolved

   Se ha resuelto la cuestión que afecta a TestRail y todos los servicios están en pleno funcionamiento. Gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de agosto de 2026 a las 15:17 UTCresolved

   Identificamos un problema DNS que puede haber impedido a algunos usuarios acceder a TestRail. La cuestión se ha resuelto y todos los servicios están en pleno funcionamiento. Nos disculpamos por cualquier inconveniente y le agradecemos por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 11 de agosto de 2026 a las 18:03 UTCidentified

   Identificamos un problema de rendimiento que afecta a un subconjunto de cuentas de TestRail Cloud, resultando en tiempos de carga de página más lentos para algunos usuarios. Nuestro equipo identificó la causa subyacente e implementó una mitigación que ha estabilizado el rendimiento. Seguimos vigilando de cerca el medio ambiente mientras trabajamos hacia una resolución permanente. Apreciamos su paciencia y comprensión mientras trabajamos para resolver plenamente el problema.

2. 12 de agosto de 2026 a las 16:15 UTCmonitoring

   Seguimos monitoreando de cerca el rendimiento de las instancias de Cloud afectadas después de la mitigación aplicada anteriormente. Nuestro equipo ha identificado una resolución permanente, que está siendo objeto de examen y pruebas. Gracias por su paciencia continua mientras finalizamos este trabajo.

3. 14 de agosto de 2026 a las 15:39 UTCresolved

   Se ha resuelto la cuestión que afecta a un pequeño subconjunto de clientes y todos los servicios están en pleno funcionamiento. Gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 20 de marzo de 2026 a las 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 de marzo de 2026 a las 15:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 de marzo de 2026 a las 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 de marzo de 2026 a las 17:56 UTCidentified

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

5. 20 de marzo de 2026 a las 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 de marzo de 2026 a las 0: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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de febrero de 2024 a las 16:22 UTCinvestigating

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

2. 26 de febrero de 2024 a las 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 de febrero de 2024 a las 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 de febrero de 2024 a las 0: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 de febrero de 2024 a las 9:02 UTCmonitoring

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

6. 27 de febrero de 2024 a las 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 de febrero de 2024 a las 20:02 UTCresolved

   This incident has been resolved.

1. 19 de febrero de 2024 a las 10:48 UTCinvestigating

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

2. 19 de febrero de 2024 a las 12:34 UTCidentified

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

3. 19 de febrero de 2024 a las 13:44 UTCresolved

   This incident has been resolved.

1. 15 de febrero de 2024 a las 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 de febrero de 2024 a las 15:53 UTCmonitoring

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

3. 18 de febrero de 2024 a las 23:48 UTCresolved

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

1. 14 de febrero de 2024 a las 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. 14 de febrero de 2024 a las 10:59 UTCmonitoring

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

3. 14 de febrero de 2024 a las 12:30 UTCmonitoring

   We are continuing to monitor this issue.

4. 14 de febrero de 2024 a las 18:08 UTCmonitoring

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

5. 15 de febrero de 2024 a las 8:35 UTCresolved

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

1. 12 de octubre de 2023 a las 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 de octubre de 2023 a las 17:20 UTCidentified

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

3. 13 de octubre de 2023 a las 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. 14 de octubre de 2023 a las 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. 16 de octubre de 2023 a las 7:08 UTCmonitoring

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

6. 16 de octubre de 2023 a las 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 de junio de 2023 a las 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. 1 de junio de 2023 a las 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. 1 de junio de 2023 a las 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. 1 de junio de 2023 a las 11:43 UTCresolved

   All systems are operational.

1. 7 de septiembre de 2022 a las 12:08 UTCinvestigating

   We are currently investigating this issue.

2. 7 de septiembre de 2022 a las 13:17 UTCresolved

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

1. 5 de septiembre de 2022 a las 8:53 UTCinvestigating

   We are currently investigating this issue.

2. 5 de septiembre de 2022 a las 9:28 UTCidentified

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

3. 5 de septiembre de 2022 a las 12:57 UTCmonitoring

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

4. 5 de septiembre de 2022 a las 14:03 UTCresolved

   This incident has been resolved.

1. 17 de agosto de 2022 a las 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 de agosto de 2022 a las 16:46 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 de agosto de 2022 a las 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 de agosto de 2022 a las 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 de agosto de 2022 a las 17:58 UTCresolved

   This incident has been resolved.

1. 14 de junio de 2022 a las 12:58 UTCinvestigating

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

2. 14 de junio de 2022 a las 14:19 UTCmonitoring

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

3. 22 de junio de 2022 a las 12:15 UTCresolved

   This incident has been resolved.

1. 4 de mayo de 2022 a las 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. 4 de mayo de 2022 a las 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. 4 de mayo de 2022 a las 9:24 UTCinvestigating

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

4. 4 de mayo de 2022 a las 10:46 UTCmonitoring

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

5. 4 de mayo de 2022 a las 14:35 UTCresolved

   This incident has been resolved.

1. 8 de marzo de 2022 a las 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 de marzo de 2022 a las 16:57 UTCresolved

   This incident has been resolved.

1. 7 de marzo de 2022 a las 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 de marzo de 2022 a las 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 de marzo de 2022 a las 10:59 UTCresolved

   This incident has been resolved.

1. 7 de marzo de 2022 a las 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. 7 de marzo de 2022 a las 9:26 UTCmonitoring

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

3. 7 de marzo de 2022 a las 11:05 UTCresolved

   This incident has been resolved.

1. 2 de marzo de 2022 a las 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. 2 de marzo de 2022 a las 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. 3 de marzo de 2022 a las 11:00 UTCresolved

   This incident has been resolved.

1. 1 de marzo de 2022 a las 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. 1 de marzo de 2022 a las 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. 1 de marzo de 2022 a las 13:39 UTCinvestigating

   We are continuing to investigate this issue.

4. 1 de marzo de 2022 a las 18: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. 1 de marzo de 2022 a las 20: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. 1 de marzo de 2022 a las 20:10 UTCresolved

   This incident has been resolved.