Dashlane incident

Degradation services

Minor Resolved View vendor source →

Dashlane experienced a minor incident on July 23, 2026 affecting Sync and Two-factor authentication (2FA) and 1 more component, lasting 3h 4m. The incident has been resolved; the full update timeline is below.

Started
Jul 23, 2026, 12:58 PM UTC
Resolved
Jul 23, 2026, 04:03 PM UTC
Duration
3h 4m
Detected by Pingoru
Jul 23, 2026, 12:58 PM UTC

Affected components

SyncTwo-factor authentication (2FA)2FA recovery codes by SMSSingle sign-on (SSO)Confidential SSO (Single-sign-on)Web appChrome extensionFirefox extensionEdge extensionPassword Management (Primary Data Center)

Update timeline

  1. investigating Jul 23, 2026, 12:58 PM UTC

    We are currently investigating reports of performance degradation affecting Dashlane vault services. Users may experience slow response times or intermittent issues with logins, data synchronization, and backups. Our engineering team is actively investigating the root cause and working to restore full service. We will provide updates as soon as more information becomes available 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 Jul 23, 2026, 12:58 PM UTC

    We are currently investigating reports of performance degradation affecting Dashlane vault services. Users may experience slow response times or intermittent issues with logins, data synchronization, and backups. Our engineering team is actively investigating the root cause and working to restore full service. We will provide updates as soon as more information becomes available

  3. monitoring Jul 23, 2026, 01:52 PM UTC

    Service has been restored. We are actively monitoring the situation.

  4. monitoring Jul 23, 2026, 01:52 PM UTC

    Service has been restored. We are actively monitoring the situation.

  5. resolved Jul 23, 2026, 04:03 PM UTC

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