Degraded Performance of the DRACOON Cloud

Incident Report for DRACOON Cloud

Postmortem

We experienced an issue with the DRACOON Cloud on 25.04.2024 from 16:00 - 16:50. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future.

What happened? There has been Degraded Performance of our API and Web UI during the incident window.

Why did this happen? There happened to be some long running queries on one of our database servers in addition to smaller issues with one of our file servers, which resulted in a Degraded Performance of the before mentioned components.

What did we do? Our incident response team quickly identified the underlying issue and resolved it.

What can we do to improve? We will further investigate the issue and improve the affected database queries to prevent similar issues in the future.

We apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future.

If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.

Posted Apr 29, 2024 - 09:00 CEST

Resolved

The issue with the DRACOON Cloud has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

Posted Apr 25, 2024 - 16:48 CEST

Investigating

We are currently investigating an issue with DRACOON Cloud. Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

Posted Apr 25, 2024 - 16:00 CEST

This incident affected: API (API (group 01), API (group 02), API (group 03), API (group 04), API (group 05), API (group 06), API (group 07), API (group 08), API (group 09)) and Web App.