Histórico de interrupções do Diligent

1. 24 Eost 2026 da 15:20 UTCinvestigating

   Os usuários da região dos EUA podem ter problemas de acesso intermitentes ao usar Projetos, incluindo falhas ao carregar ou acessar conteúdo. A questão está afetando a disponibilidade para alguns usuários na região dos EUA.

2. 24 Eost 2026 da 15:56 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 24 Eost 2026 da 15:57 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Eost 2026 da 05:53 UTCinvestigating

   Atualmente estamos passando por uma falha que está impedindo os usuários de acessar nosso serviço. Os nossos engenheiros estão a investigar. Obrigado pela vossa compreensão e paciência!

2. 20 Eost 2026 da 05:56 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 20 Eost 2026 da 05:57 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 20 Eost 2026 da 06:03 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 13:42 UTCinvestigating

   Atualmente estamos investigando um problema que afeta o Boards Cloud que pode impedir alguns usuários de acessar com sucesso a plataforma. Pedimos desculpas pela inconveniência e apreciamos sua paciência enquanto trabalhamos para resolver este problema.

2. 16 Gouere 2026 da 13:48 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 16 Gouere 2026 da 15:18 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 16 Gouere 2026 da 15:51 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Gouere 2026 da 21:29 UTCinvestigating

   Boards and Entities users in the US region are experiencing service connectivity issues, resulting in intermittent access and degraded application availability. The team is actively investigating the issue and working to restore normal service.

2. 4 Gouere 2026 da 21:44 UTCidentified

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

3. 4 Gouere 2026 da 21:46 UTCmonitoring

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

4. 4 Gouere 2026 da 21:52 UTCresolved

   This incident has been resolved.

1. 22 Mezheven 2026 da 13:09 UTCinvestigating

   Users are unable to access the site in the US region. We are currently investigating. Thank you for your understanding and patience!

2. 22 Mezheven 2026 da 13:20 UTCidentified

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

3. 22 Mezheven 2026 da 17:38 UTCmonitoring

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

4. 22 Mezheven 2026 da 17:44 UTCresolved

   This incident has been resolved.

1. 28 Mae 2026 da 03:23 UTCidentified

   Users are currently experiencing service degradation in non-US regions. The Results app remains accessible via the highbond.com domain while we investigate the issue. Thank you for your understanding and patience!

2. 28 Mae 2026 da 04:29 UTCmonitoring

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

3. 28 Mae 2026 da 05:00 UTCresolved

   This incident has been resolved.

1. 27 Mae 2026 da 20:03 UTCinvestigating

   We are currently investigating this issue.

2. 27 Mae 2026 da 20:16 UTCidentified

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

3. 27 Mae 2026 da 20:18 UTCmonitoring

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

4. 27 Mae 2026 da 20:26 UTCresolved

   This incident has been resolved.

1. 24 Mae 2026 da 08:14 UTCinvestigating

   Users are intermittently experiencing service degradation in the US region. We are currently investigating. Thank you for your understanding and patience.

2. 24 Mae 2026 da 08:47 UTCidentified

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

3. 24 Mae 2026 da 11:53 UTCidentified

   Boards, BoardEffect, and Entities are currently stable, and all services have recovered except **BoardDocs**, which continues to experience intermittent performance issues. Our teams are actively working to resolve the remaining impact and will provide additional updates as progress is made.

4. 24 Mae 2026 da 13:09 UTCmonitoring

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

5. 24 Mae 2026 da 15:51 UTCresolved

   This incident has been resolved.

1. 22 Mae 2026 da 09:54 UTCidentified

   Users are not able to access the site in the US region. We are currently investigating. Thank you for your understanding and patience!

2. 22 Mae 2026 da 11:06 UTCmonitoring

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

3. 22 Mae 2026 da 11:16 UTCresolved

   This incident has been resolved.

1. 20 Mae 2026 da 02:54 UTCinvestigating

   Users are not able to access the application in the APAC region. We are currently investigating. Thank you for your understanding and patience!

2. 20 Mae 2026 da 02:55 UTCidentified

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

3. 20 Mae 2026 da 03:42 UTCmonitoring

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

4. 20 Mae 2026 da 04:03 UTCresolved

   This incident has been resolved.

1. 12 Mae 2026 da 10:00 UTCinvestigating

   Users are not able to access the application in the EU region. We are currently investigating. Thank you for your understanding and patience!

2. 12 Mae 2026 da 10:03 UTCidentified

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

3. 12 Mae 2026 da 10:14 UTCmonitoring

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

4. 12 Mae 2026 da 10:37 UTCresolved

   This incident has been resolved.

1. 1 Mae 2026 da 15:30 UTCinvestigating

   We are currently investigating this issue.

2. 1 Mae 2026 da 22:55 UTCinvestigating

   We are currently investigating an issue that is preventing users from accessing BoardDocs. We understand the impact of this disruption and sincerely apologize for the inconvenience. This is a high-priority issue, and our senior engineers are actively working to address it. We will share more information as soon as it becomes available. Please continue to monitor this page for the most up to date information.

3. 1 Mae 2026 da 23:58 UTCidentified

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

4. 1 Mae 2026 da 23:58 UTCmonitoring

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

5. 4 Mae 2026 da 12:27 UTCmonitoring

   A fix has been implemented and our senior engineers continue to monitor the results. We appreciate your continued support and apologize for any disruption. Please continue to monitor this page for the most up to date information.

6. 4 Mae 2026 da 21:57 UTCmonitoring

   The BoardDocs system is online and stable at this time. We are actively monitoring the results and are prepared to act should any further issues occur. Please continue to monitor this page for the most up to date information.

7. 7 Mae 2026 da 15:17 UTCinvestigating

   We are currently investigating an issue that is preventing users from accessing BoardDocs. We sincerely apologize for the inconvenience. We will share more information as soon as it becomes available. Please continue to monitor this page for the most up to date status.

8. 7 Mae 2026 da 15:52 UTCmonitoring

   The BoardDocs system is online and available at this time. We are performing additional maintenance to increase capacity. Please continue to monitor this page for the most up to date information. If you are unable to login, please follow the instructions at this page (https://www.diligent.com/support/boarddocs-incident-update) to ensure there is no local browser issue impacting your ability to log in.

9. 15 Mae 2026 da 15:23 UTCresolved

   This incident has been resolved.

1. 27 Ebrel 2026 da 13:07 UTCinvestigating

   Users are unable to access their sites in the US region. We are currently investigating. Thank you for your understanding and patience!

2. 27 Ebrel 2026 da 16:41 UTCidentified

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

3. 27 Ebrel 2026 da 17:35 UTCidentified

   The issue has been identified and a fix is being implemented

4. 27 Ebrel 2026 da 20:08 UTCinvestigating

   Please be aware that teams are still actively engaged and working on this issue. We understand this issue is frustrating and are doing everything we can to resolve it as quickly as possible.

5. 27 Ebrel 2026 da 20:27 UTCinvestigating

   We are currently investigating this issue.

6. 28 Ebrel 2026 da 13:03 UTCinvestigating

   Our senior engineering team continues to actively investigate a performance issue impacting BoardDocs. The issue is being treated as a priority, and we have engaged the vendor to assist with resolution

7. 28 Ebrel 2026 da 18:30 UTCidentified

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

8. 28 Ebrel 2026 da 18:30 UTCmonitoring

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

9. 28 Ebrel 2026 da 22:08 UTCresolved

   This incident has been resolved.

1. 20 Ebrel 2026 da 10:47 UTCinvestigating

   Users are intermittently unable to access D1P in the across region. We are currently investigating. Thank you for understanding and patience.

2. 20 Ebrel 2026 da 11:04 UTCidentified

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

3. 20 Ebrel 2026 da 11:08 UTCmonitoring

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

4. 20 Ebrel 2026 da 12:38 UTCresolved

   This incident has been resolved.

1. 19 Ebrel 2026 da 00:38 UTCinvestigating

   Users in the UK region are experiencing temporary difficulty accessing the Diligent Data Room. During this time, the application is unavailable and the issue is being addressed as quickly as possible.

2. 19 Ebrel 2026 da 02:33 UTCidentified

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

3. 19 Ebrel 2026 da 03:27 UTCmonitoring

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

4. 19 Ebrel 2026 da 03:36 UTCresolved

   This incident has been resolved.

1. 13 Ebrel 2026 da 08:23 UTCinvestigating

   We are currently investigating this incident. Thank you for your patience.

2. 13 Ebrel 2026 da 08:34 UTCidentified

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

3. 13 Ebrel 2026 da 08:42 UTCmonitoring

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

4. 13 Ebrel 2026 da 09:14 UTCresolved

   This incident has been resolved.

1. 17 Meurzh 2026 da 05:37 UTCinvestigating

   We are currently experiencing a service disruption from Salesforce and following up with the Salesforce team. We apologize for any inconvenience.

2. 17 Meurzh 2026 da 06:36 UTCidentified

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

3. 17 Meurzh 2026 da 08:28 UTCmonitoring

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

4. 17 Meurzh 2026 da 08:32 UTCresolved

   This incident has been resolved.

1. 27 Cʼhwevrer 2026 da 23:22 UTCinvestigating

   We are currently investigating this issue.

2. 28 Cʼhwevrer 2026 da 01:13 UTCidentified

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

3. 28 Cʼhwevrer 2026 da 01:13 UTCmonitoring

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

4. 28 Cʼhwevrer 2026 da 01:47 UTCresolved

   This incident has been resolved.

1. 27 Cʼhwevrer 2026 da 13:41 UTCinvestigating

   Users are currently unable to reach the Support Team via the UK support number (+44-800-234-6580). We are actively investigating the issue with our third party provider. In the meantime, you can reach us through our global support number (+1-973-939-9381) or via email ([email protected]). Thank you for your understanding and patience!

2. 27 Cʼhwevrer 2026 da 15:55 UTCidentified

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

3. 28 Cʼhwevrer 2026 da 13:22 UTCmonitoring

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

4. 28 Cʼhwevrer 2026 da 13:36 UTCresolved

   This incident has been resolved.

1. 24 Cʼhwevrer 2026 da 19:52 UTCinvestigating

   Third Party Manager is unavailable in the US Region

2. 24 Cʼhwevrer 2026 da 19:55 UTCidentified

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

3. 24 Cʼhwevrer 2026 da 19:56 UTCmonitoring

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

4. 24 Cʼhwevrer 2026 da 20:25 UTCresolved

   This incident has been resolved.