Search

Companies / Keeper / incidents

Keeper: Keeper API website load time and API errors in US region

Impact: criticalStatus: postmortemStarted Resolved (1.0 h)6 updatesSource: stspg.io (opens in new tab)
Summary

Keeper reported a critical incident involving slow responses and HTTP 504 errors, listing Admin Console and Web Vault components in EU, GovCloud and US, plus the US website. It lasted from 2024-09-24 13:43 UTC to 2024-09-24 14:43 UTC (1 h 0 min); NGINX network traffic overload caused errors, and a resolution was rolled out.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Keeper Admin Console (GovCloud)Keeper Infrastructure (GovCloud) - Keeper Admin Console (GovCloud)Keeper Admin Console (EU)Keeper Infrastructure (EU Data Center) - Keeper Admin Console (EU)Keeper Infrastructure (US Data Center) - Keeper Security Website (US)Keeper Security Website (US)Keeper Infrastructure (GovCloud) - Keeper Web Vault (GovCloud)Keeper Web Vault (GovCloud)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)Keeper Infrastructure (EU Data Center) - Keeper Web Vault (EU)Keeper Web Vault (EU)

Timeline of updates

  1. investigating

    We are currently investigating reports of slow server response times and request timeouts

  2. identified

    Root cause has been identified and we are actively working on a resolution.

  3. monitoring

    A resolution has been rolled out - the team is monitoring system performance.

  4. monitoring

    We are continuing to monitor for any further issues.

  5. resolved

    This incident has been resolved.

  6. postmortem

    On Tues, Sept 24 at 6:06AM PDT, the DevOps Engineering team started receiving notifications regarding API slowness and HTTP 504 errors coming from the Keeper AWS infrastructure. After an investigation, it was determined that our NGINX instances were throwing the errors due to an overload of network traffic. It was then determined that the network traffic increase was caused by an update to the Keeper Desktop application which was published on Monday, the day before. The DevOps team scaled the AWS infrastructure several times over the period of 60 minutes to address the issue. The issue was fully stabilized and resolved by 7:20AM PDT. After a full analysis of the product update process, the engineering team has decided to change the update mechanism of the Keeper Desktop application to utilize a new distributed content delivery network which does not impact the other Keeper AWS infrastructure. This change will be implemented over the next 2 weeks and in preparation of the next Keeper Desktop application update.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Keeper profile · Recent Keeper incidents · Markdown · JSON