[mdaniel]

It's not that they were preventing the local database unlock, they were preventing acquiring a credential to the server in order to sync any changes to/from the central store. As mentioned in a sibling comment, it's was also specifically the login endpoints that were labeled as bogus, so my suspicion is that any credential acquired before the incident may have continued to work

My 1Password for Linux was emitting `Some(Status=500)` on the console, so I'd presume they botched a rollout and then just rolled it back. Unknown why it took an hour, but maybe it's the old adage about 59 minutes to find the bolt, one minute to replace it

I don't know if 1Password/AgileBits publishes postmortems nor if they'd be of sufficient detail even if they did