Skip to content

Outage tracker / Dashlane / In the US

Is Dashlane down in the US?

Vendor lists an old incident, not shown as liveWhat Dashlane reports

Dashlane still lists an incident opened on 2026-05-31 with no update since 2026-06-01; we do not show it as live.

As of the last successful poll, 2026-11-07 17:44 UTC.

Dashlane's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Dashlane at Nov 7, 2026, 5:45 PM UTC.

Over the last 24 hours we completed 266 checks from Ashburn and San Jose and 266 answered cleanly, 100.00% availability.

Of the 2 other regions we check Dashlane from, all 2 read checks passing right now.

Email me when Dashlane reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Dashlane's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing124 checks in 24h, 100.00%

Last checked Nov 7, 2026, 5:45 PM UTC.

Dashlane from Ashburn and San Jose over the last 30 days

Over the last 30 days, Dashlane answered our Ashburn probe in 1,041 ms on average, and 1 check in 20 took longer than 1,403 ms.

Over the last 30 days, Dashlane answered our San Jose probe in 1,165 ms on average, and 1 check in 20 took longer than 1,777 ms.

Ranked by average response time across the 4 cities we check Dashlane from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 771 ms and Tokyo slowest at 1,552 ms.

From Ashburn and San Jose we ran 1,317 checks of Dashlane in 6 days, and 1,317 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Ashburn local time (EST), Dashlane was slowest around 7 PM, at 1,202 ms on average over the last 14 days, and quickest around 4 PM, at 899 ms.

Day (UTC)ChecksAvailabilityAverage response
Sat, Nov 7200100.00%1,147 ms
Fri, Nov 6256100.00%1,056 ms
Thu, Nov 5253100.00%1,150 ms
Wed, Nov 4254100.00%1,062 ms
Tue, Nov 3248100.00%1,058 ms
Mon, Nov 2106100.00%1,148 ms

Dashlane outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Dashlane outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Dashlane from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 118 checks
TokyoChecks passing100.00% of 70 checks

Other countries we check Dashlane from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Dashlane's public endpoints. They are not user reports, and they are not Dashlane's own status page.

See Dashlane's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Dashlane has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter