Skip to main content
Dashlane logo

Is Dashlane Down?

No — Dashlane is up

Reachable from all 8 checked regions

Average response time: 244ms

Last checked · checks run every 6 hours

Official status page: https://status.dashlane.com

Dashlane uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
248ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

55-day clean streak
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Aug 24: 100.00% uptime, 32 checks
Aug 25: 100.00% uptime, 24 checks
Aug 26: 100.00% uptime, 32 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 21 checks
Sep 4: 100.00% uptime, 28 checks
Sep 5: 100.00% uptime, 32 checks
Sep 6: 100.00% uptime, 32 checks
Sep 7: 100.00% uptime, 22 checks
Sep 8: 100.00% uptime, 36 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 40 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 40 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw
254ms
DNS 96ms TCP 1ms TLS 6ms TTFB 243ms
ewr
210ms
DNS 128ms TCP 2ms TLS 9ms TTFB 199ms
fra
250ms
DNS 168ms TCP 2ms TLS 8ms TTFB 233ms
gru
344ms
DNS 248ms TCP 2ms TLS 7ms TTFB 332ms
iad
184ms
DNS 64ms TCP 2ms TLS 7ms TTFB 169ms
jnb
229ms
DNS 64ms TCP 0ms TLS 10ms TTFB 220ms
lax
239ms
DNS 55ms TCP 1ms TLS 11ms TTFB 226ms
lhr
245ms
DNS 86ms TCP 2ms TLS 12ms TTFB 232ms

What Dashlane does

Dashlane is a password manager offering autofill across browsers and mobile, credential sharing for teams, single sign-on for businesses and dark web monitoring on top. People reach it dozens of times a day without thinking about it, so an outage is usually noticed as autofill quietly failing rather than as a service being down.

What an outage looks like

Autofill stops offering credentials on sites where it normally appears, with no error to explain it. The web app fails to load and sign-in hangs. Items saved on one device do not sync to another. Sharing a credential with a colleague fails, and two-factor recovery by SMS may not deliver, which blocks account recovery specifically.

What to do about it

Check status.dashlane.com, which lists Sync, Autofill, the web app, the browser extensions, mobile apps, Sharing, SSO and Dark Web Monitoring as separate components. Credentials already synced remain available in clients you are signed into. Avoid signing out or removing the extension mid-incident, since re-authenticating depends on the service that is currently failing.

Is it down for everyone, or just you?

If this page says Dashlane is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Dashlane outage FAQ

Is Dashlane down or has autofill broken on one site?
Autofill is a distinct component, but single-site failures are usually caused by that site changing its login form rather than by an incident. Check status.dashlane.com, then try a site where autofill normally works. If everything else fills correctly, the problem is that one page and can be fixed by saving the credential again.
Can I reach my passwords during a Dashlane outage?
On devices already signed in, yes. Dashlane keeps a local encrypted copy, so existing clients continue to fill and display credentials. What fails is syncing changes, signing in somewhere new, and sharing. If you need a password on a device you have not set up, that is the case an outage genuinely blocks.
Will items I saved during the outage sync later?
Items saved on a client while sync was failing are held locally and generally upload once the connection returns. The risk is saving different versions of the same item on two devices, which creates a conflict. Work from one device until Sync is reported healthy, rather than assuming both copies will merge cleanly.
Why can I not recover my account during an incident?
Recovery paths depend on Dashlane services, and two-factor recovery codes by SMS is listed as its own component. If recovery is degraded, account recovery is exactly what will not work, which is unfortunate timing for anyone locked out. Waiting for the status page to clear is more effective than repeated recovery attempts.
Does a Dashlane outage affect the built-in VPN?
VPN is listed as its own component and can fail independently of the password features. An existing VPN session may continue while new connections fail, and password autofill can be entirely unaffected. Match your symptom to the specific component rather than treating any Dashlane problem as one single outage.

How we measure this

  • We request Dashlane's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Dashlane publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Dashlane goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required