DRACOON experienced a critical incident on July 1, 2026 affecting API (group 01) and Instant messages and 1 more component, lasting 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 01, 2026, 09:32 AM UTC
We are currently investigating an issue with DRACOON. 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 Jul 01, 2026, 10:11 AM UTC
The issue with DRACOON 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 Jul 01, 2026, 10:26 AM UTC
The issue with DRACOON 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 23, 2026, 09:24 AM UTC
**July 1, 2026, 11:20 – 12:30 CEST** - Post-Mortem On July 1, 2026, between approximately 11:20 and 12:15 CEST, DRACOON Cloud had an issue that caused a temporary service interruption. Our team has worked to identify the root cause and put a resolution in place. In this post-mortem, we want to explain 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?** For about 55 minutes, DRACOON Cloud was unavailable or only partially available for users. After we restored service, we kept monitoring the platform until 12:30 CEST to make sure it was fully stable. No customer data was lost or compromised. **Why did this happen?** We rolled out a planned configuration change to our internal platform infrastructure. The goal of the change was to further strengthen the security of our environment. However, the change did not behave as expected in production and affected communication between some internal components of DRACOON Cloud. This caused the service interruption. **What did we do?** Our monitoring alerted us to the problem, and our engineers began investigating right away \(11:20 CEST\). They traced the interruption back to the recent configuration change and corrected it, which restored normal communication between the affected components. DRACOON Cloud was fully available again at 12:15 CEST. We then monitored the platform to confirm it was stable and declared the incident resolved at 12:30 CEST. **What can we do to improve?** * We will expand our pre-production testing and validation for infrastructure configuration changes so that they better match real production conditions. * We will roll out changes of this kind in smaller, gradual steps, so that we detect any unexpected behavior early. * We will improve our automated checks to find problems like this faster and to allow quicker rollback. We apologize for any inconvenience this incident may have caused. We are committed to keeping our services stable and reliable and will continue to take proactive measures to prevent similar incidents in the future. If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.