DRACOON experienced a major incident on January 14, 2025 affecting API (group 01) and API (group 02) and 1 more component, lasting 49m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 14, 2025, 02:52 PM UTC
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.
- monitoring Jan 14, 2025, 02:58 PM UTC
The issue with DRACOON Cloud has been resolved, and we are monitoring the situation to ensure it remains stable. We apologize for any inconvenience this may have caused and appreciate your patience.
- resolved Jan 14, 2025, 03:41 PM UTC
The issue with 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.
- postmortem Sep 17, 2025, 10:00 AM UTC
We experienced an issue with the DRACOON Cloud on 14.01.2025 from 15:52 - 15:58. 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 an outage of the DRACOON Cloud during the incident window. Why did this happen? There happened to be some unexpected issues with one of our database servers, which caused the DRACOON Cloud to be unavailable during the incident window. What did we do? Our incident response team quickly started investigating, identified the underlying issue and resolved it by restoring connectivity to the database server. What can we do to improve? We will further investigate the issue and improve our infrastructure to prevent similar issues to occur 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.