You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting on February 23rd, around 3am Central time, the server responsible for the high-speed database backing the cluster services such as Bitwarden and the Kubernetes API server was taken offline for a hardware memory upgrade. Completing the upgrade took around 10 minutes. Upon restarting the server, the two high performance database disks were no longer appearing as if it contained data. An investigation revealed that the data was not being written to the disk appropriately, as it had been partitioned incorrectly. Service was restored on March 2nd at 7:18pm.
What was the impact?
Almost every service ran from this cluster went offline for an extended period of 8 days. Due to the nature of the issue being related to persistent data storage, everything after February 17th at 4pm was lost, for a total loss of 6 days. This includes Bitwarden accounts created after February 17th.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters