Dashlane incident

Partial Disruption of 2FA Services

Minor Resolved View vendor source →

Dashlane experienced a minor incident on June 26, 2026 affecting Two-factor authentication (2FA) and Password Management (Primary Data Center), lasting 6h 16m. The incident has been resolved; the full update timeline is below.

Started
Jun 26, 2026, 09:54 AM UTC
Resolved
Jun 26, 2026, 04:11 PM UTC
Duration
6h 16m
Detected by Pingoru
Jun 26, 2026, 09:54 AM UTC

Affected components

Two-factor authentication (2FA)Password Management (Primary Data Center)

Update timeline

  1. investigating Jun 26, 2026, 09:54 AM UTC

    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. Back to current status Status History Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @DashlaneStatus Close

  2. investigating Jun 26, 2026, 09:54 AM UTC

    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.

  3. monitoring Jun 26, 2026, 01:29 PM UTC

    Service has been restored, and a workaround has been completed for Two-Factor Authentication (2FA). We are actively monitoring the situation.

  4. monitoring Jun 26, 2026, 01:29 PM UTC

    Service has been restored, and a workaround has been completed for Two-Factor Authentication (2FA). We are actively monitoring the situation.

  5. resolved Jun 26, 2026, 04:11 PM UTC

    This issue is now resolved. Thank you for your patience.