DRACOON experienced a major incident on January 16, 2025 affecting API (group 03), lasting 2h 5m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 16, 2025, 12:23 PM UTC
We are currently investigating an issue with the API. 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.
- identified Jan 16, 2025, 01:49 PM UTC
We have identified the issue with the API. Our engineers have already found a resolution and we will perform an emergency maintenance to resolve the problem at 15:00. There might be a downtime of a few minutes.
- monitoring Jan 16, 2025, 02:09 PM UTC
The issue with the API 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 16, 2025, 02:29 PM UTC
The issue with the API 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, 09:58 AM UTC
We experienced an issue with the API on 16.01.2025 from 13:23 - 15:09. 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 API during the incident window. Why did this happen? There happened to be some unexpected issues with one of our backend components, which caused the API to be unavailable druing the incident window. What did we do? Our incident response team quickly started investigating, identified the underlying issue and resolved it by providing a hotfix during an emergency maintenance. 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.