https://approjects-vendor-status-watch.static.hf.space/v/keeper.htmlIncidents from Keeper's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/sgtmc5mmlktqkeeper:2026-09-09T09:32:18.183-07:00Wed, 09 Sep 2026 16:32:18 +0000This incident has been resolved.https://stspg.io/sfd3sgm5mpbhkeeper:2026-07-30T23:00:00.000-07:00Fri, 31 Jul 2026 06:00:00 +0000# 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 cohttps://stspg.io/4z131lx31smtkeeper:2026-07-08T11:51:48.000-07:00Wed, 08 Jul 2026 18:51:48 +0000API errors have been resolved. The Keeper Gateway and KSM client version is no longer returning an error.https://stspg.io/00z3qcqm8j47keeper:2026-06-26T15:43:05.888-07:00Fri, 26 Jun 2026 22:43:05 +0000The issue is resolved.https://stspg.io/9fn1hl2hblcdkeeper:2026-06-19T08:05:50.000-07:00Fri, 19 Jun 2026 15:05:50 +0000The issue was resolved at 12:30PM PST.https://stspg.io/gv00jgz9gls4keeper:2026-03-30T20:00:00.000-07:00Tue, 31 Mar 2026 03:00:00 +0000On 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.https://stspg.io/7pcmbl7mcjs5keeper:2026-03-23T10:07:28.854-07:00Mon, 23 Mar 2026 17:07:28 +0000At 9:05 AM PST, alerts were triggered for issues affecting KeeperPAM connections managed through Keeper’s ECS deployments in the US-EAST region. There were no recent changes to the application or environment. Investigation identified a low-level concurrency bug in the Keeper EPM service that caused request failures under high simultaneous load. These failures led to instability in the ECS services supporting KeeperPAM connections. As a temporary mitigation, we blocked the error condition, restoring KeeperPAM connectivity by approximately 1:00 PM PST. The engineering team then developed and deployed an updated Keeper Router version to address the underlying issue and prevent EPM agents from triggering server errors. The fix was fully validated by 3:00 PM PST, at which point all KeeperPAMhttps://stspg.io/xmv5k609bq2rkeeper:2026-03-16T11:25:39.762-07:00Mon, 16 Mar 2026 18:25:39 +0000At 11:08 AM PST, DevOps and customers reported sporadic error messages occurring after login for KeeperPAM customers with connections and tunnels enabled. While vault login itself was not affected, the errors were triggered asynchronously after login due to a communication issue with the KeeperPAM router endpoint. Further investigation determined that a "scheduler" database within the AWS RDS environment - used for certain PAM scheduling operations - was encountering an unexpected error. The operations team resolved the underlying database issue and restarted the affected services. This scheduler service was inadvertently impacting connection establishment. To prevent similar issues in the future, we will be implementing software changes to ensure that scheduling-related errors cannot afhttps://stspg.io/ppmr21yzdrkvkeeper:2026-02-18T21:30:15.665-08:00Thu, 19 Feb 2026 05:30:15 +0000Maintenance in the GovCloud region was scheduled to begin at 8:00 PM PST with a planned duration of 30 minutes. During the maintenance window, certain services required additional reconfiguration beyond the original scope. Core services were restored within the planned 30-minute window. However, due to the extended reconfiguration activities, some users experienced API errors during login for approximately 15 minutes following service restoration.https://stspg.io/s03qflw92x5vkeeper:2025-12-02T14:48:46.000-08:00Tue, 02 Dec 2025 22:48:46 +0000On December 2, our **EU region** experienced an unexpected outage during planned infrastructure updates. The issue began at **1:24 PM PT** and service was fully restored by **4:10 PM PT**. **What Happened** During an update to our server configuration, a region-specific configuration error caused the EU environment to begin throwing API errors. Although the underlying issue was identified quickly, each corrective change required a full autoscaling group rollout \(up to 30 minutes per cycle\) which extended the total recovery time. **Resolution** Our engineering team implemented the necessary fixes and restored service. We have also updated our infrastructure-as-code to ensure this issue cannot recur in future deployments. We apologize for the disruption and appreciate your patience https://stspg.io/09y8zn8d18l7keeper:2025-10-20T10:25:40.746-07:00Mon, 20 Oct 2025 17:25:40 +0000Clearing this alert as most AWS services are restored.https://stspg.io/wylsd3hwpx38keeper:2025-10-20T02:20:49.722-07:00Mon, 20 Oct 2025 09:20:49 +0000All Keeper email delivery services in US-EAST-1 were restored around 4AM PST.https://stspg.io/p6vlghlxh5vykeeper:2025-09-10T08:42:41.658-07:00Wed, 10 Sep 2025 15:42:41 +0000On **September 10 at 8:42 AM PDT**, our monitoring detected elevated errors with the **Auth API in the EU region**. The issue was identified promptly and fully resolved by **8:49 AM PDT**. Total impact duration was approximately **7 minutes**. ### Impact * **Region affected:** EU * **Service affected:** Authentication API * **Customer impact:** Customers in the EU experienced failed authentication attempts during the incident window. ### Timeline \(PDT\) * **08:42** – Incident detected. Elevated Auth API errors in the EU region reported. * **08:43** – Engineering and DevOps teams engaged. * **08:46** – Root cause isolated to a Terraform-related configuration change involving a VPC endpoint. * **08:49** – Configuration change rolled back; Auth API errors resolved. ### Root Cause The ohttps://stspg.io/3xx2lxq4wkvmkeeper:2025-08-21T10:36:36.285-07:00Thu, 21 Aug 2025 17:36:36 +0000Resolved - At 9:49 AM PST, we experienced login API request failures due to errors on an RDS database in the US region. The database failover completed successfully, and all systems were fully operational by 10:00 AM PST.