Dashlane Outage History
4 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Dashlane Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Slowness when using the Dashlane apps or not able to LoginWe 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… | 7h 11m | Resolved |
| Oct 12, 2026 | Planned maintenance for our systems is scheduled on Monday, October 12th, 2026 at 7:00 UTC for approx. 30 minutesScheduled Maintenance | 30 min | Scheduled |
| Sep 28, 2026 | Scheduled Performance Testing & Minimal Impact NoticeScheduled Maintenance | 2h 0m | Scheduled |
| May 31, 2026 | Investigating Unexpected Account Notifications and Login IssuesWe 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… | 3782h 23m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Dashlane incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Dashlane Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Dashlane acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Dashlane outage in this window ran 157d 14h, against a mean recovery of 39d 12h. If you depend on Dashlane in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.