LastPass | Status

Today, a database query was executed that was intended to update billing information for a small subset of companies. Unfortunately, the query contained a logic error which inadvertently added incorrect billing information across a large portion of our customer base. This change had no effect on the core LastPass experience, functionality, or billing for our customers. We have since removed the incorrect billing information for all affected customers and will closely monitor the situation to ensure there is no recurrence. LastPass sincerely apologizes for any inconvenience this issue may have caused. We are closely examining our existing process for these types of requests and will be publishing the results of our root cause analysis when it is complete.

We have confirmed that the issue has been resolved completely and all systems are 100% operational at this time. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.

We have confirmed that the issue has been resolved completely and all systems are 100% operational at this time. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.

A server configuration change was deployed recently that caused frontend applications to stop working. The change was rolled back, and applications are now working normally. We have confirmed that the issue has been resolved, and all systems are 100% operational at this time.

We have confirmed that the issue has been resolved completely, and all systems are 100% operational at this time. Our engineers identified an issue with the caching layer data base which was causing performance delays when attempting to load the download website, this has been corrected, and load times are now normal.

We have confirmed that the issue has been resolved. An image file referring to a bad path caused all help articles to become unavailable due to bad path construction on all articles. Teams working with the vendor were able to fix the bad reference and republish, fixing the issue. We will be working to implement a permanent solution to address this issue going forward including quality assurance checks within our deployment pipeline and implementation of new publishing guidelines.

We confirm that the issue is resolved and all systems are 100% operational. As always, we will conduct an internal review of this issue to help prevent / minimize future recurrence.

A recent production deployment caused some servers to lose host name resolution resulting in some product related emails not being sent out. This has been rolled back, and we have confirmed that the issue has been resolved completely, and all systems are 100% operational at this time.

We have confirmed that the issue has been resolved. We will conduct an internal review of this issue to help prevent or minimize future recurrence.