--- service: "DRACOON" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T06:43:40.254Z" url: "https://instatus.com/now/ko/dracoon.com" official_status_page: "https://status.dracoon.com" website: "https://www.dracoon.com/de/home" --- # DRACOON 다운되었나요? 아니요, 정상이에요. 최근 1시간 동안 0건 보고됨. ## 공식 업데이트 - **Scheduled Maintenance** (SCHEDULED, 2026-11-04T21:00:00.000Z): We will be undergoing scheduled maintenance during this time. A short downtime for a couple of minutes can occur. - **Scheduled Maintenance** (COMPLETED, 2026-10-28T21:00:00.000Z): The scheduled maintenance has been completed. - **Partial Outage of Email notifications** (RESOLVED, 2026-10-26T09:29:04.000Z): **20 - 26 October 2026: Post-Mortem** We experienced an issue with email notifications between 20 October and 26 October 2026. 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?** During this period, some recipients did not receive email notifications from DRACOON. The issue mainly affected organisations whose incoming mail runs through certain corporate email security gateways. For these recipients, many notifications were rejected and not delivered. All other DRACOON functions were unaffected. ‌**Why did this happen?** Before accepting a mail, some email security gateways check that the sender's domain is valid. A DNS service operated by a third-party provider began giving an incorrect answer for part of our notification sender domain's configuration. Because of that answer, these gateways wrongly treated our sender domain as invalid and rejected the notifications. Our own configuration and our mail delivery service were working correctly throughout. **What did we do?** After the first customer reports, we analyzed the delivery logs together with our email delivery partner and found that the rejections followed a clear pattern. We traced them to the third-party DNS issue. On 26 October, we changed the configuration of our notification sender domain so that it no longer depends on the affected third-party service. After the change, delivery returned to normal, and we monitored it closely to confirm the issue was resolved. **What can we do to improve?** * We are reviewing our email-related configurations to remove dependencies on external services. * We are improving our monitoring of email delivery, so that unusual rejection rates are detected and investigated sooner. 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. ## DRACOON 장애 FAQ ### 지금 DRACOON 다운됐나요? 아니요, 정상이에요. 최근 1시간 동안 0건 보고됨. ### DRACOON이(가) 모두에게 안 되나요, 저만 안 되나요? 당신만 겪는 문제일 수 있어요. DRACOON 제보가 평소 수준이니, 페이지를 새로고침하거나 연결을 확인하거나 로그아웃 후 다시 로그인해 보세요. ### DRACOON에서 사람들은 어떤 문제를 제보하나요? 지난 1시간 동안 DRACOON에서 무엇이 안 되는지 말한 사람이 없습니다. 안 되는 게 있다면 위에서 선택해 다른 사람들도 볼 수 있게 해주세요. ### DRACOON의 마지막 장애는 언제였나요? DRACOON 제보는 최근 30일간 급증하지 않았어요. ### DRACOON에 상태 페이지가 있나요? 네. DRACOON은(는) 공식 상태 페이지에 업데이트를 올리며, 현재 상태는 정상입니다. [상태 페이지로 이동](https://status.dracoon.com/) ### DRACOON이(가) 안 되면 어떻게 하나요? 이 페이지와 DRACOON의 상태 페이지에서 업데이트를 확인하고, 몇 분 기다린 후 다시 시도하세요. 재설치는 하지 마세요. 장애라면 해결은 서비스 쪽에서 합니다. ### DRACOON 문제는 어떻게 제보하나요? 이 페이지 상단의 “저도 같은 문제가 있습니다”를 누르고 무엇이 안 되는지 선택하세요. 제보는 1분 안에 실시간 차트에 표시되며, 댓글로 어떤 상황인지 다른 사람에게 알려줄 수도 있습니다. ### Instatus Now는 어떻게 알죠? 이 페이지의 사용자 제보와 매분 확인하는 DRACOON 공식 상태 페이지를 함께 살펴봐요.