Bitwarden Was Down
status.bitwarden.com
status.bitwarden.com
my workplace selfhosts it, so its not affecting us.
What is more reliable (ignoring hindsight), Bitwarden's service or your workplace's systems?
(Edited - added 'upstream')
For instance, skip traversing the internet for in-office deployments/credential use. Also: incentives. PMs or engineers at another company have incentives that don't always align with reliability for yours.
Vaultwarden deserves a mention, happy hoster for years here.
I'll shell out cash for hosted databases... even though I'm fine with building everything else myself. Topology stuff alone usually makes this worth it.
Virtual machines and snapshots can take you a long way, though :)
When everything becomes hyper concentrated in singular environments, a problem with that environment scales the blast radius to everyone.
For example when AWS US-East-1 occasionally goes down. It’s been a few years since the last time that happened, but when it happens it’s inescapable.
Still works on mobile, so it's not the end of the world.
Didn't for me. Granted, I have several identities and I was switching between them. Perhaps the one I was switching too was no longer cached. If so, I consider that a bug. I also consider what happened to be a bug - the Android App crashed.
Oh wait, it's still crashing. So the outage isn't the cause.
Did I mention I'm growing to dislike this Android Bitwarden App with a passion. It's slow at opening (why not open the cached version and download the up-to-date version in the background), it sometimes takes so long to do something Android brings up the "it's taking too long, want me to kill it" dialogue, it takes a long with for the keyboard to display the "Fill in with Bitwarden" prompt, presumably because it takes so long to process intents.
Probably the primary reason I dont use these services even the self hosted version and stick to KeePass for now.
[0]: https://keepassxc.org/docs/KeePassXC_UserGuide#_database_sha...
Also, your local copy (if it works) is read-only. You can't edit anything without an internet connection. So no, it's more like you have a read-only local copy, but it's an internet-first service - this is my main issue with Bitwarden and the reason I'm migrating back to KeePass.
Sure, it's at least dockerised, but it requires root privileges (so no running it in a secured kubernetes env) and forces you to use MSSQL as the db (so pay up for that or hope that express works).
It's also unfriendly to automated deployment, with several manual steps and regular rebooting requires.
I've been burnt by things breaking as Bitwarden updates the client and vaultwarden tries to keep up without any advance notice of the changes until someone reports it's broken.
There was a breaking change when I updated to iOS 18, but by the time I’ve noticed that, it was already fixed in an update.
maybe its time for a new manager. Any recs?
[0]https://community.bitwarden.com/t/cannot-login-to-vault-by-s...
But I'll add another anecdote. I have had the same experience. I have never noticed any downtime from bitwarden but my 3 node kubernetes cluster that would host vaultwarden has gone down multiple times. Sometimes just for maintenance.
I self host a lot of stuff but my password vault is not one of them yet.