rewindex

CompaniesDashlaneIncidents

Dashlane: Slowness when using the Dashlane apps or not able to Login

CriticalStatus: resolvededitedStarted Resolved (7.2 h)6 updatesstatus.dashlane.com (opens in new tab)
Summary

Dashlane reported a critical incident causing app slowness or inability to log in, starting 2026-10-27 10:21 UTC. It was still open when archived, open for 0 min at the last update; Dashlane said its team was investigating, with no cause or fix stated.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: 2FA recovery codes by SMSAccount CreationAdmin ConsoleAndroid appAutofillChrome extensionConfidential SSO (Single-sign-on)Credential Risk DetectionCustomer SupportDark Web InsightsDark Web MonitoringEdge extensionEmail notificationsFirefox extensioniOS (Apple) appNudgesOmnixPaid plans' purchasePasskeysPassword ManagementSafari appSCIMSharingSingle sign-on (SSO)SyncTwo-factor authentication (2FA)VPNWeb appWebsite

Timeline of updates

  1. identified

    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

  2. monitoring

    Between 10:00 and 10:25 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 log in.  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.

  3. investigating

    Following our earlier service disruption, a subset of customers are reporting an unexpected error message when logging in. Our team is currently investigating and working to surpass the situation. Thank you for your understanding.

  4. investigating

    Our team continues to actively investigate this situation, and we suspect it could be connected with the incident declared by Cloudflare, which has confirmed a third-party issue affecting certain vendor firewalls following a recent firmware upgrade. When traffic passes through an affected firewall, the firewall blocks the connection during inspection, and the browser shows "This site can't be reached" Possible Workaround: If you're affected, try connecting from a different network (for example, a mobile hotspot). IT admins can also contact their firewall vendor about the recent firmware update. Cloudflare incident: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew (opens in new tab)

  5. monitoring

    Cloudflare has resolved the underlying issue, and we're seeing access recovery for affected users. We're continuing to monitor to confirm all users are fully restored. If you're still seeing "This site can't be reached" or cannot login at Dashlane, please contact our support team. Switching to a different network remains a workaround in the meantime. Cloudflare incident: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew (opens in new tab)

  6. resolved

    This incident is now resolved. We could identify two separate causes: 1. Service disruption: An internal software change caused the initial disruption. The service was restored by reverting the change. 2. Subsequent login issues for some users: A separate third-party issue, confirmed by Cloudflare, caused the errors. Cloudflare has resolved the issue, and access has been restored. Cloudflare incident: cloudflarestatus.com/incidents/dk2obcyw2aew Your data was not affected at any point. We're reviewing both issues to prevent recurrence. If you're still experiencing problems, please contact our support team.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.dashlane.com (opens in new tab).

Cite this

Status incident (vendor impact label: critical) posted by Dashlane, started 2026-10-27 10:21 UTC, resolved after 7.2 h, 6 update(s); edited after publishing.

Title
Slowness when using the Dashlane apps or not able to Login
Vendor
Dashlane
Date
URL
https://rewindex.com/company/dashlane/incidents/6ae07b24ab895c05f8cfeca9

Dashlane profileRecent Dashlane incidentsAll outages on October 27, 2026Dashlane in October 2026MarkdownJSON