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

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.

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.

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

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