Dracoon の障害履歴

1. 2026年10月26日 9:29 UTCinvestigating

   現在、Eメール通知で問題点を調べています。 当社のチームは、より多くの情報を収集し、可能な限り迅速に問題を解決するために取り組んでいます。 誠に申し訳ございませんが、ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

2. 2026年10月26日 11:31 UTCinvestigating

   当社のチームは、メール通知で問題解決に積極的に取り組んでいます。 特定のメールサーバ設定を使用しているお客様は、DRACOON からのメール通知を受けられない場合があります。メール配信パートナーと連携して、可能な限り迅速に解決できます。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 今後、情報やアップデートを随時配信いたします.

3. 2026年10月26日 15:38 UTCmonitoring

   Eメール通知で問題を識別し、それを解決するために修正を適用しました。 状況を監視し、安定した状態を維持し、追加の問題を検知します。 過去数日間に、DRACOONからのメール通知が届かない場合もございます。 ほとんどの場合、メールが受信メールを受け入れる前に特定のDNSチェックを含む特定の企業メールセキュリティゲートウェイを介して実行される組織が影響されます。 根本的な原因は、通知の送信者ドメインに影響を及ぼすサードパーティのDNSの問題で最も可能性が高いです。 通知は、再び配信されるべきです。 問題が完全に解決されると、配信を密接に監視し、更新を投稿します。 この期間中に配信されていない通知は、自動的に再送信されません。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

4. 2026年10月27日 7:46 UTCresolved

   メール通知の問題は完全に解決しました。 すべてのシステムが正常に動作しています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 今後も、どんな問題にも関わらず、サポートチームにお任せください.

5. 2026年10月27日 7:49 UTCpostmortem

   **20 - 26 10月2026日: ポストオルテム** 10月20日(火)〜10月26日(日)のメール通知にてお知らせいただきました。 私たちのチームは、根本的な原因を特定し、解像度を実装するために徹底的に取り組んできました。 このポスト・モテムでは、何が起こったのか、なぜそれが起こったのか、それを解決するために何をしたのか、そして今後同様の出来事を防止するために何をすべきかについて詳細を共有したいと思います。 **何が起こったのか?** この期間中は、DRACOONからのメール通知を受け取っていませんでした。 主に、特定の企業メールセキュリティゲートウェイを介してメールが実行される影響を受けた組織の問題。 これらの受信者に対して、多くの通知が拒否され、配信されません。 他のDRACOON関数は影響を受けません。 **こんなことがあったの?** メールを受信する前に、送信者のドメインが有効であることを確認するメールセキュリティゲートウェイがいくつかあります。 サードパーティプロバイダが運用するDNSサービスは、通知送信ドメインの構成の一部に誤った回答を与え始めました。 そのため、これらのゲートウェイは、送信元ドメインを無効に処理し、通知を拒否しました。 弊社独自の構成とメール配信サービスが全力で正しく機能しました。 **何をしたの?** 最初の顧客レポートの後、弊社メール配信パートナーと配送ログを分析し、拒否がクリアなパターンに続くことを確認しました。 サードパーティのDNSの問題にそれらを追跡しました。 10月26日、通知送信元ドメインの構成を変更し、影響を受けた第三者サービスに依存しないようにしました。 変更後、納品を正常に返し、問題が解決されたことを確認するために密接に監視しました。 **改善にはどうしたらいいですか?** ※外部サービスの依存関係を除去するために、メール関連の設定を見直しています。 ※メール配信のモニタリングを改善し、異常な拒否率が検出され、早期に調査されます。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 当社は、当社のサービスの安定性と信頼性を確保し、今後同様の事故を防ぐための積極的な対策を講じています。 ご質問やご不明な点がございましたら、サポートチームまでお気軽にお問い合わせください.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月22日 11:12 UTCresolved

   最近公開されたセキュリティ脆弱性 CVE-2026-109618 と CVE-2026-109619 は PHP に影響を与えています。 DRACOON は PHP を使用しないため、脆弱性の影響を受けません。 あなたの部分にアクションは必要ありません。 今後もセキュリティアドバイザリーを密接に監視し、このアセスメント変更をお知らせし続けます.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月6日 9:54 UTCinvestigating

   We have identified an issue with uploads and downloads on DRACOON Cloud. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

2. 2026年8月6日 9:55 UTCresolved

   The issue with uploads and downloads on DRACOON Cloud 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.

1. 2026年7月16日 7:51 UTCresolved

   データセンタープロバイダーの可用性の問題が発生したため、DRACOON Cloudの部分的な停電を経験しました。 当社のエンジニアは、回避策を適用することにより、短期的な課題を解決できるようになりました。 この復元された可用性とすべてのシステムが正常に動作していた後。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 今後も、どんな問題にも関わらず、サポートチームにお任せください.

2. 2026年7月16日 7:54 UTCpostmortem

   2026-07-16でDRACOON Cloudを00:05から00:30まで体験しました。 私たちのチームは、根本的な原因を特定し、解像度を実装するために徹底的に取り組んできました。 このポスト・モテムでは、何が起こったのか、なぜそれが起こったのか、それを解決するために何をしたのか、そして今後同様の出来事を防止するために何をすべきかについて詳細を共有したいと思います。 **何が起こったのか?** 当社のデータセンタープロバイダは、DRACOON Cloudインフラストラクチャが稼働している地域および可用性ゾーンの可用性の問題を経験しました。 その結果、DRACOONクラウドの一部が利用できなくなったり、事故時に性能を劣化させたりしました。 **何をしたの?** 当社のエンジニアは、状況を分析し、可能な限り迅速に可用性を完全に回復するために技術的な回避策を適用しました。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 当社は、当社のサービスの安定性と信頼性を確保し、今後同様の事故を防ぐための積極的な対策を講じています。 ご質問やご不明な点がございましたら、サポートチームまでお気軽にお問い合わせください.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月1日 9:32 UTCinvestigating

   現在、DRACOONの問題点を調査中です。 当社のチームは、より多くの情報を収集し、可能な限り迅速に問題を解決するために取り組んでいます。 誠に申し訳ございませんが、ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

2. 2026年7月1日 10:11 UTCmonitoring

   DRACOONの問題は解決され、状況を監視し、安定した状態を確保しています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

3. 2026年7月1日 10:26 UTCresolved

   DRACOONの問題は完全に解決しました。 すべてのシステムが正常に動作しています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 今後も、どんな問題にも関わらず、サポートチームにお任せください.

4. 2026年9月23日 9:24 UTCpostmortem

   ** 7月 1, 2026, 11:20 – 12:30 CEST** - ポストオルテム 2026年7月1日、約11:20～12:15 CEST、DRACOON クラウドは一時的なサービス中断を引き起こした問題でした。 私たちのチームは、根本原因を特定し、解決を所定の位置に置くために働いています。 このポスト・モテムでは、何が起きたのか、なぜ起きたのか、それを解決するために何をしたのか、そして今後同様の出来事を防止するために何をすべきかについて説明したいと思います。 **何が起こったのか?** 約55分、DRACOON Cloudが利用できなくなったり、一部ご利用者のみがご利用いただけます。 復旧後、プラットフォームを監視し、12:30 CESTまで監視し、完全に安定した状態に保ちます。 顧客データが紛失または侵害されることはありません。 **こんなことがあったの?** 社内プラットフォームインフラへの計画設定変更をロールアウトしました。 変化の目標は、環境のセキュリティをさらに強化することとなりました。 しかしながら、DRACOON Cloud の内部コンポーネントの制作と影響を受けた通信では、変更が期待どおり動作しなかった。 これにより、サービスの中断が発生しました。 **何をしたの?** 当社のモニタリングは問題に警告し、エンジニアはすぐに \(11:20 CEST\) を調べ始めました。 それらは、最近の構成変更に戻り、影響を受けたコンポーネント間の正常な通信を復元したことを修正しました。 DRACOON Cloud は12:15 CEST で公開されました。 その後、プラットフォームを監視し、それが安定していたことを確認し、12:30 CESTで解決された事故を宣言しました。 **改善にはどうしたらいいですか?** ※ インフラ構成変更の事前テストと検証を拡充し、実際の生産条件にマッチするよう努めます。 ※この種の変更を小さく、段階的なステップでロールアウトし、予期しない動作を早期に検知します。 ※自動チェックを改良し、より迅速にロールバックできるようにします。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 当社は、本サービスを安定的かつ確実な状態に保ち、今後同様の事故を防止するために、引き続き積極的な対策を講じてまいります。 ご質問やご不明な点がございましたら、サポートチームまでお気軽にお問い合わせください.

公式のインシデント更新を自動翻訳しています。

1. 2026年4月16日 15:58 UTCinvestigating

   We are currently investigating an issue with our Virus Protection feature. 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. 2026年4月16日 20:57 UTCresolved

   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.

1. 2026年3月24日 8:48 UTCinvestigating

   We are currently investigating an issue with Web App. 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. 2026年3月24日 8:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026年3月24日 9:42 UTCmonitoring

   The issue with Web App has been temporarily 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.

4. 2026年3月25日 12:03 UTCresolved

   The issue with our Web App 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.

5. 2026年3月27日 10:28 UTCpostmortem

   We experienced an issue with our WebApp on 2026-03-24 from around 9:30 to 11:00 CET. 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?** We experienced service instability caused by a bug in a third-party dependency. This resulted in intermittent errors and degraded performance of the Web App. **Why did this happen?** A bug in a third-party dependency caused unexpected errors in our Web App, leading to occasional crashes. This issue was triggered under specific conditions that were not caught in prior testing. **What did we do?** We resolved the issue temporarily by implementing a safeguard and later by properly solving the issue with this dependency. Stability was restored once the temporary fix was deployed, with full recovery at around 10:40 CET. **What can we do to improve?** We will expand our test coverage to better capture edge cases, ensuring that unusual or unexpected scenarios, especially those that lead to this incident, are identified and prevented before deployment. 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.

1. 2026年1月12日 10:42 UTCresolved

   We have been experiencing issues with our DRACOON service from 11:00 to 11:40 on 2026-01-12. Our team was working to resolve the issue as quickly as possible. We apologize for any inconvenience this may have caused.

1. 2026年1月8日 10:42 UTCidentified

   We have identified an issue with DRACOON Cloud. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

2. 2026年1月8日 10:43 UTCidentified

   We are continuing to work on a fix for this issue.

3. 2026年1月8日 10:44 UTCresolved

   The issue with DRACOON Cloud 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.

1. 2025年11月27日 8:30 UTCinvestigating

   Our team is still actively working to resolve the issue with Virus Protection Scanning. We apologize for any inconvenience this may cause and appreciate your patience. We will provide more information and updates as soon as they become available.

2. 2025年11月27日 8:50 UTCidentified

   We have identified the issue with Virus Protection Scanning. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

3. 2025年11月27日 12:34 UTCmonitoring

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

4. 2025年11月27日 13:58 UTCresolved

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

1. 2025年11月20日 14:52 UTCresolved

   From 14:55 to 15:05 today, we experienced some issues and a partial outages of DRACOON Cloud. Our team quickly identified and resolved the issue. We apologize for any inconvenience this may have caused.

1. 2025年11月19日 8:42 UTCinvestigating

   We are currently investigating an issue with DRACOON 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. 2025年11月19日 9:55 UTCidentified

   We have identified the issue with DRACOON Virus Protection. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

3. 2025年11月19日 11:09 UTCmonitoring

   The issue with DRACOON Virus Protection has been resolved, all pending scans should be completed within the next few minutes. We are monitoring the situation to ensure it remains stable. We apologize for any inconvenience this may have caused and appreciate your patience.

4. 2025年11月19日 11:27 UTCresolved

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

1. 2025年8月13日 10:00 UTCidentified

   We have identified an issue with degraded performance of our virus protection feature for some customers. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

2. 2025年8月13日 13:45 UTCmonitoring

   The issue with degraded performance of our virus protection feature 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. 2025年8月13日 14:59 UTCresolved

   The issue with degraded performance of our virus protection feature 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. 2025年9月2日 11:28 UTCpostmortem

   We experienced an issue with our Virus Protection feature on 13.08.2025 at around 12:00 CEST. 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?** At 12:00 CEST, monitoring alerted the team about increased latency in the Virus Protection service. Investigation revealed that unusually high load from a spike in file scanning requests overwhelmed the systems processing capacity, leading to degraded performance for a subset of customers. **Why did this happen?** The Virus Protection service was able to keep up with the increased load for scanning files, but the responses were not processed fast enough by another service, leading to missing/delayed verdicts for the files that had to be scanned. **What did we do?** The team manually scaled out the service to restore capacity. At 15:45, latency metrics returned to normal and the functionality was fully restored. **What can we do to improve?** We are investigating the root cause of the slow response processing and will reconfigure the service in question to make sure to eliminate the bottleneck. 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.

1. 2025年8月4日 6:58 UTCinvestigating

   We are currently investigating an issue with our Support Portal (Dracoon Server). 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. 2025年8月4日 7:25 UTCresolved

   The issue with our Support Portal has been fully resolved. We apologize for any inconvenience this may have caused and appreciate your patience.

1. 2025年7月28日 7:54 UTCinvestigating

   We are currently investigating an issue with our Support Portal. 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. 2025年7月28日 10:58 UTCresolved

   The issue with our Support Portal has been fully resolved. We apologize for any inconvenience this may have caused and appreciate your patience.

1. 2025年7月16日 7:31 UTCresolved

   There was an issue with DRACOON on 2025-07-12 from around 14:30 to 15:40. Our team worked to gather information and resolved the issue as quickly as possible. We apologize for any inconvenience this may have caused.

2. 2025年9月9日 14:59 UTCpostmortem

   We experienced an issue with DRACOON Cloud on 2025-07-12 from around 14:30 to 15:40. 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? DRACOON Cloud experienced performance degradation. Some users reported slow response times and connection timeouts during the incident window. Why did this happen? The incident was caused by increased load and scaling issues. A part of the system was unable to handle the traffic volume, leading to resource exhaustion and subsequent service degradation. What did we do? Our team immediately identified the scaling bottleneck and implemented emergency load balancing measures. We scaled up the infrastructure resources to restore normal service levels by 15:40. What can we do to improve? We will implement automated scaling policies to handle traffic spikes, enhance monitoring and alerting systems for early detection of load issues, and conduct regular capacity planning reviews to prevent similar incidents. 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.

1. 2025年7月7日 10:05 UTCinvestigating

   We are currently investigating an issue with DRACOON. 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. 2025年7月7日 10:59 UTCmonitoring

   The issue with DRACOON 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. 2025年7月7日 11:10 UTCresolved

   The issue with DRACOON 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. 2025年9月9日 15:01 UTCpostmortem

   We experienced an issue with DRACOON Cloud on 2025-07-07 from around 12:00 to 13:00. 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? DRACOON Cloud experienced performance degradation. Some users reported slow response times and connection timeouts during the incident window. Why did this happen? The incident was caused by increased load and scaling issues. A part of the system was unable to handle the traffic volume, leading to resource exhaustion and subsequent service degradation. What did we do? Our team immediately identified the scaling bottleneck and implemented emergency load balancing measures. We scaled up the infrastructure resources to restore normal service levels by 13:00. What can we do to improve? We will implement automated scaling policies to handle traffic spikes, enhance monitoring and alerting systems for early detection of load issues, and conduct regular capacity planning reviews to prevent similar incidents. 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.

1. 2025年6月23日 13:14 UTCinvestigating

   Our team is actively working to resolve the issue with the OnlyOffice preview. We apologize for any inconvenience this may cause and appreciate your patience. We will provide more information and updates as soon as they become available.

2. 2025年6月23日 13:15 UTCidentified

   We have identified the issue with the OnlyOffice preview. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

3. 2025年6月25日 11:40 UTCresolved

   The issue with the OnlyOffice preview 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. 2025年9月9日 15:33 UTCpostmortem

   We experienced an issue with Office file previews on 2025-06-25 from around 09:00 to 13:40. 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? We experienced an issue with office file previews, making the feature unavailable for all users. Why did this happen? A recent update of the license key used by our backend service responsible for the office previews did not work as expected, even though the same update has been working on our Staging environment. What did we do? We immediately investigated and identified that the updated license key was causing authentication failures in production. We got in contact with the service provider to solve the issue as quickly as possible. What can we do to improve? We identified the issue that lead to the discrepancy between production and staging environment and made sure this will not happen again 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.

1. 2025年3月31日 6:06 UTCinvestigating

   We are currently investigating an issue with DRACOON Cloud. 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. 2025年3月31日 6:11 UTCmonitoring

   The issue with DRACOON Cloud 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. 2025年3月31日 8:56 UTCresolved

   The issue with DRACOON Cloud 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. 2025年9月9日 15:18 UTCpostmortem

   We experienced an issue with DRACOON Cloud on 2025-03-31 from around 07:30 to 08:15. 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? DRACOON Cloud experienced performance degradation during early usage hours, affecting user access and normal operation. Why did this happen? Application containers hit memory limits during high traffic periods, causing automatic restarts and service interruptions as the container orchestration system cycled through unhealthy instances. The memory limits were set too conservatively and hadn't been updated to account for certain traffic spikes. What did we do? Our engineering team quickly identified the container restart pattern through application logs and monitoring dashboards. We immediately increased the memory limits for affected services and scaled up the number of container replicas to distribute the load. What can we do to improve? We will improve our monitoring, update memory limits based on actual usage patterns, and create automated scaling policies that proactively increase resources before hitting limits. 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.

1. 2025年3月12日 17:00 UTCinvestigating

   We are currently investigating an issue with DRACOON Cloud. 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. 2025年3月12日 17:00 UTCresolved

   The issue with DRACOON Cloud 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.