Störungsverlauf von Diligent

1. 24. August 2026 um 15:20 UTCinvestigating

   Benutzer in der US-Region können bei der Nutzung von Projekten intermittierende Zugriffsprobleme auftreten, einschließlich Fehler beim Laden oder Zugriff auf Inhalte. Das Problem beeinflusst die Verfügbarkeit für einige Benutzer in der US-Region.

2. 24. August 2026 um 15:56 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 24. August 2026 um 15:57 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. August 2026 um 05:53 UTCinvestigating

   Wir erleben derzeit einen Ausfall, der Benutzer daran hindert, auf unseren Dienst zuzugreifen. Unsere Ingenieure untersuchen derzeit. Vielen Dank für Ihr Verständnis und Ihre Geduld!

2. 20. August 2026 um 05:56 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 20. August 2026 um 05:57 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 20. August 2026 um 06:03 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 13:42 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit Boards Cloud, das einige Benutzer daran hindern könnte, erfolgreich auf die Plattform zuzugreifen. Wir entschuldigen uns für die Unannehmlichkeiten und schätzen Ihre Geduld, während wir daran arbeiten, dieses Problem zu lösen.

2. 16. Juli 2026 um 13:48 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 16. Juli 2026 um 15:18 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 16. Juli 2026 um 15:51 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 4. Juli 2026 um 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. Juli 2026 um 21:44 UTCidentified

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

3. 4. Juli 2026 um 21:46 UTCmonitoring

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

4. 4. Juli 2026 um 21:52 UTCresolved

   This incident has been resolved.

1. 22. Juni 2026 um 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. Juni 2026 um 13:20 UTCidentified

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

3. 22. Juni 2026 um 17:38 UTCmonitoring

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

4. 22. Juni 2026 um 17:44 UTCresolved

   This incident has been resolved.

1. 28. Mai 2026 um 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. Mai 2026 um 04:29 UTCmonitoring

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

3. 28. Mai 2026 um 05:00 UTCresolved

   This incident has been resolved.

1. 27. Mai 2026 um 20:03 UTCinvestigating

   We are currently investigating this issue.

2. 27. Mai 2026 um 20:16 UTCidentified

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

3. 27. Mai 2026 um 20:18 UTCmonitoring

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

4. 27. Mai 2026 um 20:26 UTCresolved

   This incident has been resolved.

1. 24. Mai 2026 um 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. Mai 2026 um 08:47 UTCidentified

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

3. 24. Mai 2026 um 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. Mai 2026 um 13:09 UTCmonitoring

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

5. 24. Mai 2026 um 15:51 UTCresolved

   This incident has been resolved.

1. 22. Mai 2026 um 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. Mai 2026 um 11:06 UTCmonitoring

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

3. 22. Mai 2026 um 11:16 UTCresolved

   This incident has been resolved.

1. 20. Mai 2026 um 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. Mai 2026 um 02:55 UTCidentified

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

3. 20. Mai 2026 um 03:42 UTCmonitoring

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

4. 20. Mai 2026 um 04:03 UTCresolved

   This incident has been resolved.

1. 12. Mai 2026 um 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. Mai 2026 um 10:03 UTCidentified

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

3. 12. Mai 2026 um 10:14 UTCmonitoring

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

4. 12. Mai 2026 um 10:37 UTCresolved

   This incident has been resolved.

1. 1. Mai 2026 um 15:30 UTCinvestigating

   We are currently investigating this issue.

2. 1. Mai 2026 um 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. Mai 2026 um 23:58 UTCidentified

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

4. 1. Mai 2026 um 23:58 UTCmonitoring

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

5. 4. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 15:23 UTCresolved

   This incident has been resolved.

1. 27. April 2026 um 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. April 2026 um 16:41 UTCidentified

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

3. 27. April 2026 um 17:35 UTCidentified

   The issue has been identified and a fix is being implemented

4. 27. April 2026 um 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. April 2026 um 20:27 UTCinvestigating

   We are currently investigating this issue.

6. 28. April 2026 um 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. April 2026 um 18:30 UTCidentified

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

8. 28. April 2026 um 18:30 UTCmonitoring

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

9. 28. April 2026 um 22:08 UTCresolved

   This incident has been resolved.

1. 20. April 2026 um 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. April 2026 um 11:04 UTCidentified

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

3. 20. April 2026 um 11:08 UTCmonitoring

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

4. 20. April 2026 um 12:38 UTCresolved

   This incident has been resolved.

1. 19. April 2026 um 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. April 2026 um 02:33 UTCidentified

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

3. 19. April 2026 um 03:27 UTCmonitoring

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

4. 19. April 2026 um 03:36 UTCresolved

   This incident has been resolved.

1. 13. April 2026 um 08:23 UTCinvestigating

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

2. 13. April 2026 um 08:34 UTCidentified

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

3. 13. April 2026 um 08:42 UTCmonitoring

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

4. 13. April 2026 um 09:14 UTCresolved

   This incident has been resolved.

1. 17. März 2026 um 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. März 2026 um 06:36 UTCidentified

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

3. 17. März 2026 um 08:28 UTCmonitoring

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

4. 17. März 2026 um 08:32 UTCresolved

   This incident has been resolved.

1. 27. Februar 2026 um 23:22 UTCinvestigating

   We are currently investigating this issue.

2. 28. Februar 2026 um 01:13 UTCidentified

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

3. 28. Februar 2026 um 01:13 UTCmonitoring

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

4. 28. Februar 2026 um 01:47 UTCresolved

   This incident has been resolved.

1. 27. Februar 2026 um 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. Februar 2026 um 15:55 UTCidentified

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

3. 28. Februar 2026 um 13:22 UTCmonitoring

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

4. 28. Februar 2026 um 13:36 UTCresolved

   This incident has been resolved.

1. 24. Februar 2026 um 19:52 UTCinvestigating

   Third Party Manager is unavailable in the US Region

2. 24. Februar 2026 um 19:55 UTCidentified

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

3. 24. Februar 2026 um 19:56 UTCmonitoring

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

4. 24. Februar 2026 um 20:25 UTCresolved

   This incident has been resolved.