Keeper Status Page Status Page

Jul 31, 2026 · resolved Jul 31

# Post-Incident Report **July 31, 2026** ## Summary On July 30, 2026 at 11:33 PM CT, the KeeperPAM connection routing service in the EU region started throwing errors. The Router/Gateway errors lasted approximately 12 hours and 45 minutes, with full service restored at approximately 12:18 PM CT on July 31. During this window, the main Keeper EU platform \(vault access, authentication, and all other Keeper services\) remained fully operational throughout. ## What Happened On July 22, a routine deployment to our connection routing service \(“Keeper Router”\) included an updated dependency that changed how the service retrieves its startup configuration. A misconfiguration in the endpoint caused EU region to look for a FIPS endpoints, which are not available. As a result, when service containers in the EU region restarted following the deployment, they were unable to retrieve their startup configuration and entered a failed state. Two factors allowed this failure to go undetected for over a week. First, existing containers continued serving traffic while replacement containers silently failed to start, so there was no immediate customer impact from the July 22 deployment. QA also passed all production verification tests. Second, the configuration-load failure was logged at INFO level rather than ERROR or CRITICAL, so no PagerDuty alerts were generated. On the night of July 30, the last healthy containers cycled out, the service's load balancer had zero healthy targets, and the endpoint began returning HTTP 503 errors. Automated health-check monitoring detected the outage within seconds and paged our on-call team. ## What We're Changing 1. **Alerting on failed container rollovers.** We are deploying CloudWatch alarms across all regions and environments that fire when container tasks repeatedly fail to start, to detect silent deployment failures. 2. **Log severity for startup failures.** Any failure to load required startup configuration will now log at ERROR/CRITICAL severity instead of INFO which trigger the proper actionable alerts. We apologize to our EU customers for the disruption.

Jul 8, 2026 · resolved Jul 8

API errors have been resolved. The Keeper Gateway and KSM client version is no longer returning an error.

Jun 26, 2026 · resolved Jun 26

The issue is resolved.

Jun 19, 2026 · resolved Jun 19

The issue was resolved at 12:30PM PST.

Mar 31, 2026 · resolved Mar 31

On March 30 at 8:00 PM PST, Keeper performed a scheduled minor upgrade to our multi-region AWS RDS clusters as part of routine maintenance. The upgrade itself completed in approximately 3 minutes, followed by a standard application restart process that took about 15 minutes. While this process is typically non-disruptive, recent changes to service health checks caused unexpected customer impact during the restart window. This maintenance was not communicated in advance due to an internal miscommunication and the expectation of no impact. We apologize for the disruption and are taking steps to ensure all future maintenance—regardless of expected impact—is communicated ahead of time, as well as reviewing our health check configurations to prevent similar issues.

Is Keeper Status Page down right now?

No — Keeper Status Page is up. All systems operational as of Aug 19, 9:41 PM UTC.

What is Keeper Status Page's current status?

Keeper Status Page: All Systems Operational. Alert24 checks Keeper Status Page's status page continuously and can notify you the moment it changes.

How do I get alerted when Keeper Status Page goes down?

Alert24 monitors Keeper Status Page and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.