Changes / Keeper / Keeper vault login errors - resolved
Keeper: Critical incident: Keeper vault login errors - resolved
Summary
Keeper reported critical US-region login errors affecting Keeper Admin Console and Keeper Web Vault from 2025-02-24 04:48 UTC to 2025-02-24 05:05 UTC (16 min), recommending “work offline.” A backend API and resulting database query triggered high database load; service was resolved, with a permanent fix planned for Monday, Feb 24.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Keeper vault login errors - resolved
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2025-02-24 04:48 UTC
Before: not present
After: 2025-02-24 05:05 UTC
Before: not present
After: Keeper Admin Console (US), Keeper Infrastructure (US Data Center) - Keeper Admin Console (US), Keeper Infrastructure (US Data Center) - Keeper Web Vault (US), Keeper Web Vault (US)
Before: not present
After: We are still working on the issue which is causing login errors in the US region. Please use Keeper's "work offline" while we are working to resolve the issue.
Before: not present
After: The issue has been resolved and root cause determined. We will update the postmortem on this issue shortly.
Before: not present
After: We identified a backend API and resulting database query which triggered a high database load and affected production services. We are publishing a permanent fix on Monday, Feb 24.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Keeper vault login errors - resolved (this change) Keeper reported critical US-region login errors affecting Keeper Admin Console and Keeper Web Vault from 2025-02-24 04:48 UTC to 2025-02-24 05:05 UTC (16 min), recommending “work offline.” A backend API and resulting database query triggered high database load; service was resolved, with a permanent fix planned for Monday, Feb 24. | Major incident |