--- service: "DRACOON" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T12:18:47.111Z" url: "https://instatus.com/now/zh/dracoon.com" official_status_page: "https://status.dracoon.com" website: "https://www.dracoon.com/de/home" --- # DRACOON 故障了吗？ 没有，一切正常. 过去一小时 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 故障常见问题 ### DRACOON 现在挂了吗？ 没有，一切正常. 过去一小时 0 份反馈报告。 ### DRACOON 是所有人都坏了，还是只有我？ 看起来只有你遇到。DRACOON 的反馈量正常，可以试试刷新页面、检查网络连接，或退出后重新登录。 ### 大家反馈了 DRACOON 的哪些问题？ 过去一小时内没有人说明 DRACOON 哪里坏了。如果你遇到问题，请在上方选择，让其他人看到。 ### DRACOON 上次故障是什么时候？ 过去 30 天内，DRACOON 的反馈没有出现激增。 ### DRACOON 有状态页面吗？ 有。DRACOON 会在官方状态页面发布更新，目前显示：运行正常。 [前往状态页面](https://status.dracoon.com/) ### DRACOON 无法使用时我可以怎么办？ 查看本页和 DRACOON 的状态页面获取更新，等几分钟再试一次。不用重新安装：如果是服务中断，要由他们那边修复。 ### 如何反馈 DRACOON 的问题？ 点击本页顶部的“我也要反馈问题”，再选择哪里坏了。你的反馈会在一分钟内显示在实时图表上，也可以留言告诉其他人你遇到的情况。 ### Instatus Now 是怎么知道的？ 我们把此页面上用户的反馈，与每分钟检查一次的 DRACOON 官方状态页结合起来。