Keeper incident

Login errors in US region

Major Resolved View vendor source →

Keeper experienced a major incident on February 10, 2025 affecting Keeper Web Vault (US) and Keeper Admin Console (US), lasting 19m. The incident has been resolved; the full update timeline is below.

Started
Feb 10, 2025, 05:30 PM UTC
Resolved
Feb 10, 2025, 05:49 PM UTC
Duration
19m
Detected by Pingoru
Feb 10, 2025, 05:30 PM UTC

Affected components

Keeper Web Vault (US)Keeper Admin Console (US)

Update timeline

  1. identified Feb 10, 2025, 05:30 PM UTC

    We are aware of a high number of errors in the US region. The issue will be fixed shortly.

  2. resolved Feb 10, 2025, 05:49 PM UTC

    We have resolved the issue and plan to deploy a backend update shortly.

  3. postmortem Feb 10, 2025, 09:53 PM UTC

    At 9:21AM PST we received notifications of API errors coming from our backend systems. The issue resolved itself without any required action at 9:31AM PST. During that 10 minute period, there was a database lock in the primary writer instance causing new login sessions to fail. Recently, Keeper upgraded all production RDS Aurora databases to MySQL 8.x. This updated database engine is sensitive to one particular SQL query that was causing large table scans to occur. The code changes and QA process was already under way when this issue occurred. The backend code change which addresses this issue passed QA at 12:48PM PST and we released the fix to prevent this issue from occurring again \(Release Jira ticket REL-4633\). We’re keeping a close eye and will issue additional updates as necessary.