История сбоев Dashlane

1. 27 октября 2026 г. в 17:34 UTCresolved

   27 октября 2026 10:21 UTC Выявлено - В настоящее время мы сталкиваемся с трудностями при входе на платформу. Наша команда активно изучает этот вопрос. Мы предоставим еще одно обновление, как только у нас будет больше информации. Мы приносим извинения за неудобства и ценим ваше терпение 27 октября 2026 10:30 Мониторинг UTC - Между 10:00 и 10:25 UTC сегодня мы испытали сбои, которые затронули Dashlane. В течение этого периода вы могли испытывать общую медлительность платформы или сталкиваться с ошибками при попытке войти в систему. Мы рады сообщить, что этот вопрос был успешно решен, и все службы в настоящее время полностью восстановлены и работают в штатном режиме, в настоящее время мы держим его под контролем. Мы приносим извинения за любые неудобства, которые это могло вызвать, и ценим ваше терпение, пока мы работали над решением проблемы. Мы предоставим дополнительную информацию после завершения нашего расследования. 27 октября 2026 12:56 UTC Следствие - После нашего предыдущего сбоя в обслуживании подмножество клиентов сообщают о неожиданном сообщении об ошибке при входе в систему. Наша команда в настоящее время расследует и работает над тем, чтобы превзойти ситуацию. Спасибо за понимание. 27 октября 2026 14:52 UTC Наша команда продолжает активно расследовать эту ситуацию, и мы подозреваем, что это может быть связано с инцидентом, объявленным Cloudflare, который подтвердил сторонние проблемы, затрагивающие определенные брандмауэры поставщиков после недавнего обновления прошивки. Когда трафик проходит через затронутый брандмауэр, брандмауэр блокирует соединение во время проверки, и браузер показывает «Этот сайт не может быть достигнут» Возможный обходной путь: Если вы пострадали, попробуйте подключиться из другой сети (например, мобильной точки доступа). ИТ-администраторы также могут связаться со своим поставщиком брандмауэра о недавнем обновлении прошивки. Инцидент Cloudflare: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew 27 октября 2026 15:38 UTC Cloudflare решила основную проблему, и мы видим восстановление доступа для пострадавших пользователей. Мы продолжаем отслеживать, чтобы подтвердить, что все пользователи полностью восстановлены. Если вы все еще видите «Этот сайт недоступен» или не можете войти в Dashlane, пожалуйста, свяжитесь с нашей службой поддержки. Переход на другую сеть остается обходным путем. Cloudflare incident: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew 27 октября 2026 17:34 UTC Решено - Теперь этот инцидент урегулирован. Мы могли бы определить две отдельные причины: 1. сбои в обслуживании: внутреннее изменение программного обеспечения вызвало первоначальное сбои. Служба была восстановлена путем возврата изменений. 2.Последующие проблемы с входом для некоторых пользователей: Отдельная сторонняя проблема, подтвержденная Cloudflare, вызвала ошибки. Cloudflare решила проблему, и доступ был восстановлен. Инцидент Cloudflare: cloudflarestatus.com/incidents/dk2obcyw2aew Ваши данные не были затронуты ни в какой момент. Мы рассматриваем обе проблемы, чтобы предотвратить повторение. Если вы все еще испытываете проблемы, пожалуйста, свяжитесь с нашей службой поддержки.

Автоматический перевод официального обновления инцидента.

1. 23 июля 2026 г. в 16:03 UTCresolved

   23 июля 2026 12:58 UTC В настоящее время мы расследуем сообщения о деградации производительности, затрагивающей службы хранилища Dashlane. Пользователи могут испытывать медленное время отклика или периодические проблемы с логинами, синхронизацией данных и резервными копиями. Наша инженерная команда активно исследует первопричину и работает над восстановлением полного сервиса. Мы предоставим обновления, как только станет доступна дополнительная информация 23 июля 2026 13:52 UTC Мониторинг - Сервис восстановлен. Мы активно следим за ситуацией. 23 июля 2026 16:03 UTC Resolved - Сейчас этот вопрос решен. Спасибо за ваше терпение.

Автоматический перевод официального обновления инцидента.

1. 6 июля 2026 г. в 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. 26 июня 2026 г. в 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. 2 июня 2026 г. в 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. 1 июня 2026 г. в 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. 23 апреля 2026 г. в 08: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. 10 апреля 2026 г. в 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. 8 апреля 2026 г. в 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. 18 марта 2026 г. в 00: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. 3 марта 2026 г. в 08: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. 4 февраля 2026 г. в 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