Dashlane の障害履歴

1. 2026年10月27日 17:34 UTCresolved

   10月27日、2026 10:21 UTC 識別 - 現在、プラットフォームにログイン困難に直面しています。 私たちのチームは積極的に問題を調査しています。 情報が増え次第に更新をいたします。 誠に申し訳ございませんが、10月27日(火)、2026 10:30 UTCモニタリングにてご迷惑をおかけいたしますが、本日は10:00〜10:25 UTCまでは、Dashlaneに影響を受けた障害が発生しました。 この期間中、ログインしようとすると、一般的なプラットフォームの低さやエラーに直面している可能性があります。 問題が正常に緩和され、すべてのサービスは完全に回復され、正常に動作していると報告しています。 問題の解決に取り組みながら、ご迷惑をおかけいたしますが、ご了承の程よろしくお願い申し上げます。 調査完了後、更なる更新をいたします。 2026年10月27日 12:56 UTC 調査 - 以前のサービス中断の後、顧客のサブセットは、ログイン時に予期しないエラーメッセージを報告しています。 私たちのチームは、現在、状況を上回るために調査および作業しています。 お問い合わせ 2026年10月27日 14:52 UTC 調査 - 私たちのチームは、この状況を積極的に調査し続けています。また、Cloudflareによって宣言されたインシデントと接続できると疑っています。これにより、最近のファームウェアのアップグレード後に特定のベンダーファイアウォールに影響を与えるサードパーティの問題が確認されています。 トラフィックが影響を受けたファイアウォールを通過すると、ファイアウォールは検査中に接続をブロックし、ブラウザは「このサイトが到達できない」を表示することができます。 影響を受けると、異なるネットワーク(例えば、モバイルホットスポット)から接続してみてください。 IT管理者は、最近のファームウェア更新に関するファイアウォールベンダーに連絡することもできます。 クラウドフレア事件: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew 10月 27, 2026 15:38 UTC モニタリング - Cloudflareは、根本的な問題を解決し、影響を受けたユーザーのアクセス回復を見ています。 すべてのユーザーが完全に復元されていることを確認するために、引き続き監視しています。 Dashlane で「このサイトにアクセスできない」またはログインできない場合は、サポートチームにお問い合わせください。 異なるネットワークへの切り替えは、その間の作業時間に残ります。 Cloudflare事件: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew 10月 27, 2026 17:34 UTC 解決する - この事件が解決しました。 1。 サービスの中断:内部ソフトウェアの変更は、初期の混乱を引き起こしました。 変更を元に戻すとサービスが復元されました。 2。 一部のユーザーのためのサブシーケントログインの問題:別のサードパーティの問題、Cloudflareによって確認、エラーを引き起こしました。 Cloudflareは問題を解決し、アクセスが復元されました。 クラウドフレア事件: cloudflarestatus.com/incidents/dk2obcyw2aew データは、いかなる時点でも影響を受けません。 再発防止のため、双方の課題を見直しています。 問題が発生した場合は、サポートチームにお問い合わせください.

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

1. 2026年7月23日 16:03 UTCresolved

   2026年7月23日 12:58 UTC 調査 - 現在、Dashlane vault サービスのパフォーマンス劣化に関するレポートを調査しています。 ユーザーは、ログイン、データの同期、およびバックアップに関する応答時間や断続的な問題が発生することがあります。 当社のエンジニアリングチームは、根本的な原因を調査し、フルサービスの復元に取り組んでいます。 2018年7月23日(水)23:59 UTC 監視 - サービスが復元されました。 状況を積極的に監視しています。 2026年7月23日 16:03 UTC 解決済み - この問題は解決しました。 ありがとうございます.

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

1. 2026年7月6日 10:55 UTCresolved

   July 6, 2026 08:48 UTC Investigating - We are currently facing difficulties logging into the platform. Our team is actively investigating the issue. We will provide another update as soon as we have more information. We apologize for the inconvenience and appreciate your patience while we work to resolve this July 6, 2026 09:07 UTC Monitoring - Between 06:50 and 8:30 UTC today, we experienced a disruption that affected Dashlane. During this period you might have experienced general platform slowness or faced errors when trying to login. We are pleased to report that the issue has been successfully mitigated and all services are now fully recovered and operating normally, we are currently keeping it under monitoring. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. We will provide a further update once our investigation is complete. July 6, 2026 10:55 UTC Resolved - This issue is now resolved. Thank you for your patience.

1. 2026年6月26日 16:11 UTCresolved

   June 26, 2026 09:54 UTC Investigating - Dashlane is actively investigating a service disruption affecting Two-Factor Authentication (2FA) via the browser extension for a subset of users. Service restoration is our immediate priority. We will issue further updates as our investigation progresses, and we thank our customers and partners for their patience during the resolution of this issue. June 26, 2026 13:29 UTC Monitoring - Service has been restored, and a workaround has been completed for Two-Factor Authentication (2FA). We are actively monitoring the situation. June 26, 2026 16:11 UTC Resolved - This issue is now resolved. Thank you for your patience.

1. 2026年6月2日 16:58 UTCresolved

   June 2, 2026 11:49 UTC Monitoring - We experienced an issue that had an impact on the Dashlane platform from approximately 10:35 UTC to 10:50 UTC. Users may have experienced SSO login errors, slow load times, inability to retrieve data, or errors when attempting to perform several actions. We have confirmed full recovery, and we are currently monitoring the situation. This issue is unrelated to the recent brute force incident. June 2, 2026 16:58 UTC Resolved - After continued monitoring, we can confirm that the service is stable and operating as expected. We sincerely apologize for any disruption this may have caused to your work today.

1. 2026年6月1日 19:29 UTCresolved

   May 31, 2026 15:19 UTC Investigating - We have received reports from several users having received an email that their account has been suspended. We have also received reports that some users are experiencing difficulties in logging in to Dashlane after resetting their master password. We are investigating this situation, and we will provide further updates as soon as we have more information. Thank you for your understanding. May 31, 2026 17:50 UTC Investigating - We are continuing to investigate the "Account suspended" notifications. Our engineering teams are actively working on a resolution and investigating the root cause of these messages. We are treating this with the highest priority and will provide further updates here as soon as more information becomes available. Thank you for your continued patience and understanding. May 31, 2026 22:30 UTC Resolved - We can confirm that certain Dashlane user accounts were targeted in a brute force attack by an external party, resulting in the suspension of those accounts as part of Dashlane’s built-in security measures. The affected accounts have now been unsuspended. Our team is actively engaged in this issue and taking measures to address it. There is no evidence of compromise of Dashlane’s systems. Thank you for your patience and understanding. June 1, 2026 07:32 UTC Monitoring - We can confirm that certain Dashlane user accounts were targeted in a brute force attack by an external party, resulting in the suspension of those accounts as part of Dashlane’s built-in security measures. The affected accounts have now been unsuspended. Our team is actively engaged in this issue and taking measures to address it. There is no evidence of compromise of Dashlane’s systems. Thank you for your patience and understanding. June 1, 2026 19:29 UTC Monitoring - Dashlane has published a Security Advisory and customer FAQ with additional details of the incident, investigation status, impact to user accounts, and steps we’ve taken to protect customers. There is no evidence that Dashlane’s internal system has been impacted. For further information, please reference our Security Advisory: https://support.dashlane.com/hc/articles/36038764990866

1. 2026年4月23日 8:10 UTCresolved

   April 15, 2026 16:20 UTC Investigating - We've received some reports of users experiencing some instability while using the Dashlane extension in Chromium browsers. We are investigating and will provide an update when we know more. In the meantime, for any customer experiencing an endless load of the extension, please try to reinstall it or use a non-Chromium browser. April 16, 2026 12:43 UTC Monitoring - We have identified that this issue is caused by a bug in the browser itself. A fix has been released in browser version 147.0.7727.101/2. Users should update their browser to this version or later and ensure the Dashlane extension is up to date to resolve the issue. April 23, 2026 08:10 UTC Resolved - After a period of monitoring, we confirmed that the issue was caused by a bug in the browser itself. A fix has been released in Chrome version 147.0.7727.101/102, and Edge version 147.0.3912.72. Users should update their browser to these versions or later and ensure the Dashlane extension is up to date. Thank you for your patience.

1. 2026年4月10日 16:07 UTCresolved

   April 10, 2026 15:40 UTC Identified - Dashlane is investigating a disruption to our SIEM feature that is impacting customers using the Splunk and KnowBe4 integrations. Restoration is our top priority, and we will provide updates on the situation as appropriate. We thank our customers and partners for their patience during the resolution of this issue. April 10, 2026 16:07 UTC Resolved - This issue is now resolved. Thank you for your patience.

1. 2026年4月8日 22:16 UTCresolved

   April 8, 2026 21:16 UTC Monitoring - Dashlane is currently investigating a disruption to our inbound Support Team emails related to an ongoing issue with Gmail services. Restoring full communication is our top priority, and our team is actively engaged in tracking the resolution. We appreciate your patience while we monitor the situation. April 8, 2026 22:16 UTC Resolved - The disruption affecting our inbound Support Team emails has been fully resolved, and normal response times have resumed. Thank you for your patience and understanding

1. 2026年3月18日 0:07 UTCresolved

   March 17, 2026 21:11 UTC Investigating - We’re investigating an issue where customers may not be able log into Dashlane on Chrome or the iOS app or may receive errors. We’ll provide an update as soon as possible. As a workaround, please try logging in using a different browser. Thank you for your patience as our team works to resolve this. March 18, 2026 00:07 UTC Resolved - This issue is now resolved. Thank you for your patience.

1. 2026年3月3日 8:40 UTCresolved

   February 26, 2026 20:20 UTC Scheduled - On Tuesday, March 3, 2026, from 8:00 to 9:00 UTC, we will be performing planned system maintenance. During this 1-hour window, you may experience transient errors for a brief period. We are working to keep any disruptions to a minimum and appreciate your patience while we improve our systems. March 3, 2026 08:06 UTC Active - Scheduled maintenance has started. We will update you as soon as it is over. March 3, 2026 08:40 UTC Completed - The scheduled maintenance is complete. All services are now operational. Thank you for your patience.

1. 2026年2月4日 17:28 UTCresolved

   February 4, 2026 15:14 UTC Monitoring - We experienced an issue that had an extended impact on the Dashlane platform from approximately 12:43 UTC to 13:30 UTC. Users may have experienced SSO login errors, slow load times, inability to retrieve data, or errors when attempting to perform several actions. We have confirmed full recovery, and we are currently monitoring the situation. February 4, 2026 17:28 UTC Resolved - After a period of careful monitoring, we are happy to confirm that the service is stable. We sincerely apologize for the disruption caused