DRACOON incident

Degraded Performance of Virus Protection

Minor Resolved View vendor source →

DRACOON experienced a minor incident on July 1, 2024 affecting Virus protection, lasting 58m. The incident has been resolved; the full update timeline is below.

Started
Jul 01, 2024, 09:00 AM UTC
Resolved
Jul 01, 2024, 09:58 AM UTC
Duration
58m
Detected by Pingoru
Jul 01, 2024, 09:00 AM UTC

Affected components

Virus protection

Update timeline

  1. investigating Jul 01, 2024, 09:43 AM UTC

    We are currently investigating an issue with Virus Protection. 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.

  2. monitoring Jul 01, 2024, 09:44 AM UTC

    The issue with Virus Protection 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.

  3. resolved Jul 01, 2024, 09:58 AM UTC

    The issue with Virus Protection 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.

  4. postmortem Jul 01, 2024, 01:32 PM UTC

    We experienced an issue with our Virus Protection Feature on 01.07.2024 from 11:00 - 11:44. 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 Virus Protection Feature during the incident window. Why did this happen? There happened to be some issues on one of our backend services, caused by an infrastructural change which resulted in Degraded Performance of our Virus Protection Feature. What did we do? Our incident response team quickly identified the underlying issue and resolved it by improving the deployment configuration of the affected service. What can we do to improve? We will further investigate the issue and improve the affected service 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.