--- service: "DRACOON" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T15:52:15.033Z" url: "https://instatus.com/now/zh-tw/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 官方狀態頁結合起來。