54 Keeper incidents · février 2023 — official updates, affected components, duration and resolution details.
The 2FA issues are down stream. AWS has reached out the aggregator that works with the carriers on this issue.
This incident has been resolved.
Les connexions établies par l'intermédiaire du routeur de garde et de la passerelle dans la région de l'UE sont en panne. Des détails supplémentaires seront affichés dans le rapport postmortem.
# Rapport post-incident **31 juillet 2026** Résumé Le 30 juillet 2026 à 23:33 CT, le service de routage de connexion KeeperPAM dans la région de l'UE a commencé à lancer des erreurs. Les erreurs de Routeur/Gateway ont duré environ 12 heures et 45 minutes, et le service complet a été rétabli vers 12h18 le 31 juillet. Au cours de cette fenêtre, la plate-forme principale de Keeper EU \(accès par défaut, authentification et tous les autres services Keeper\) est restée pleinement opérationnelle tout au long. Ce qui s'est passé Le 22 juillet, un déploiement de routine à notre service de routage de connexion \(="Keeper Router="\) a inclus une dépendance mise à jour qui a changé la façon dont le service récupère sa configuration de démarrage. Une erreur de configuration dans le paramètre a amené la région de l'UE à rechercher un paramètre FIPS, qui n'est pas disponible. En conséquence, lorsque des conteneurs de service dans la région de l'UE ont redémarré après le déploiement, ils n'ont pas pu récupérer leur configuration de démarrage et sont entrés dans un état défaillant. Deux facteurs ont permis de ne pas être détectés pendant plus d'une semaine. Premièrement, les conteneurs existants ont continué de desservir le trafic alors que les conteneurs de remplacement n'ont pas commencé en silence, de sorte qu'il n'y a pas eu d'impact immédiat sur les clients à partir du déploiement du 22 juillet. L'AQ a également réussi tous les essais de vérification de la production. Deuxièmement, la défaillance du chargement de configuration a été enregistrée au niveau INFO plutôt qu'ERROR ou CRITIQUE, de sorte qu'aucune alerte de PagerDuty n'a été générée. Dans la nuit du 30 juillet, les derniers conteneurs sains se sont déroulés, l'équilibreur de charge du service avait zéro cible saine, et le paramètre a commencé à renvoyer des erreurs HTTP 503. La surveillance automatisée des contrôles de santé a détecté les pannes en quelques secondes et a mis en page notre équipe de garde. Ce que nous changeons 1. **Alertation lors du renversement du conteneur en panne.** Nous déployons des alarmes CloudWatch dans toutes les régions et tous les environnements qui font feu lorsque les tâches de conteneur ne démarrent pas à plusieurs reprises, pour détecter les pannes de déploiement silencieuses. 2. **Log sévérité pour les échecs de démarrage.** Tout défaut de chargement de la configuration de démarrage requise se connecte maintenant à la sévérité ERROR/CRITICAL au lieu d'INFO qui déclenche les alertes actionnables appropriées. Nous nous excusons auprès de nos clients de l'UE pour cette perturbation.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous sommes conscients des erreurs de connexion Keeper Gateway et KSM en raison des réponses "invalides version client". Nous avons identifié la question et elle sera résolue dans quelques minutes.
Les erreurs d'API ont été résolues. La version client Keeper Gateway et KSM ne renvoie plus d'erreur.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
We are aware of an issue with direct record sharing for enterprise users as a result of yesterday's Vault 18.3 update. We will issue a patch before 12PM PST. To work around the issue, you can click the "Can share to users outside the enterprise" option in Role enforcements, or just use the Desktop App.
The issue was resolved at 12:30PM PST.
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.
We are investigating errors in establishing KeeperPAM connections in the US Data Center.
We have identified the cause of the KeeperPAM connection errors which are related to a networking issue within the AWS ECS environment. We are actively troubleshooting with the AWS support team and will update the ticket as soon as there is a status update.
A fix has been implemented and we are monitoring the KeeperPAM connection stability. We will update this case with additional details soon.
The issue has been resolved. See postmortem page with additional details.
At 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 KeeperPAM services were stable and operating normally.
We have identified an issue causing KeeperPAM connection errors in the US Data Center. It will be resolved shortly.
The issue has been resolved. We will update the ticket with additional details shortly.
At 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 affect connection functionality. Additional monitoring and alerting have also been implemented for the scheduler databases to help detect and prevent similar issues going forward. Full service for connection and tunneling capabilities was restored by 11:40 AM PST.
As part of our planned GovCloud region maintenance involving database upgrades, restarts of the Redshift cluster were required. As a result, downstream services required configuration updates and all services are now restored.
Maintenance 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.
During scheduled system updates, we have encountered unexpected NGINX 503 / 502 errors in the EU region. As of 4:50 PM CST, work is still in progress. During this time, users in the EU region will experience brief or intermittent access interruptions when using Keeper.
The issue has been resolved. We will update the postmortem report shortly.
On 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 while we resolved the incident.
There are intermittent connectivity issues due to the AWS outage in US-EAST-1 affecting KeeperPAM cloud connections, scheduled rotations and discovery operations.
Clearing this alert as most AWS services are restored.
AWS is reporting errors in the US-EAST region that are affecting multiple services, affecting email and SMS delivery which impacts Keeper device approvals. The AWS Service Health dashboard can be monitored here: https://health.aws.amazon.com/health/status
SMS delivery services have been restored, but AWS Lambda is still down which affects our email delivery of device approvals. We recommend using the "Keeper Push" or TOTP method of device approval.
All Keeper email delivery services in US-EAST-1 were restored around 4AM PST.
We are aware of Auth API errors in EU region and we have identified the isssue. The issue will be resolved shortly.
The issue with Auth API errors in the EU region has been resolved. Additional details will be posted in the postmortem shortly.
On **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 outage was caused by a configuration change in our production tenant during an ongoing Terraform migration. As part of the migration, a new VPC endpoint was being added to production environments. During Terraform apply, a subnet association was also being created. A network disruption occurred between the creation of the VPC endpoint and the subnet association \(behavior not seen in prior testing\) leading to temporary Auth API connectivity failures in the EU region. A new Terraform migration plan has been created that eliminates the possibility of disruption.
Resolved - 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.
Several customers have been experiencing SSO login errors this morning. The team determined the cause of the issue which is detailed in the postmortem report.
On June 30, 2025, Keeper published an updated SAML Service Provider \(SP\) certificate as part of our standard annual process. This certificate is used for signing SP requests and does not impact SSL termination. During the update, the certificate subject name was unintentionally changed from sso.keepersecurity.com to sso.staging.keepersecurity.com. While most identity providers do not validate the certificate subject name, certain providers—such as JumpCloud and Shibboleth—may enforce strict matching and reject SAML requests when the subject name does not align. On Sunday July 6, 2025, routine backend infrastructure changes caused the cert to be propagated across production systems throughout the morning hours. The issue with the subject name was identified by our team after several troubleshooting calls with customers. The DevOps team then corrected the issue by publishing the certificate with the proper subject name around 12pm PST. After reviewing the case history, this affected a small number of customers. Next year, when the SP cert change is approaching, we will notify all customers with the exact date and time when the cert will be updated, so those customers using strict SP cert matching can be prepared. We apologize for the error and we have taken steps to ensure this does not occur again.
We are investigating vault login errors
We are continuing to investigate this issue.
The issue has been resolved. The outage was caused by a high volume of database locks related to a large BreachWatch data update. The engineering team is tracking down the root cause and will be addressing a preventative solution today.
At 8:15 AM PST, our DevOps team was alerted to elevated API error rates in production. Upon investigation, we identified the following: * The production database was experiencing high table lock contention. * This was triggered by several large-scale BreachWatch data updates. * A recent backend migration had unintentionally doubled the number of parallel update operations, which exacerbated the issue. * A database failover was performed to restore service stability. The issue was fully resolved by 8:40 AM PST. The engineering team has addressed the underlying problem in the update processes and is implementing safeguards to prevent recurrence, including query optimization and improved job orchestration. We apologize for the disruption.
We are investigating login errors in the EU data center.
We have identified the issue causing login errors in the EU data center. Our team is working on a resolution.
Login errors in the EU region have been fully resolved. We will update this incident postmortem with additional information shortly.
At 4:37AM PST, Keeper experienced API errors in the EU region. Service was restored by 5:35AM PST following a database failover. The issue was caused by a bug in the new Device Management API, released the day before. During device registration, the system attempted to delete old devices, which created high database load for accounts with large device counts. The bug was identified, fixed, and a patch was deployed. We apologize for the disruption. To ensure uninterrupted access, we recommend enabling “Work Offline” mode for your account.
Some users are receiving errors when downloading file attachments. We are working on resolution.
The issue has been resolved. Additional information is in the postmortem report.
### **Incident Summary** In the US, EU, and AU regions, users experienced vault errors when attempting to download a file attachment immediately after adding it to a record. This issue affected only newly uploaded attachments in these three data center regions. The Gov, JP, and CA regions were not impacted. ### **Root Cause** During our investigation, we identified a discrepancy in how file attachment triggers were implemented across different regions. A recent Terraform change inadvertently removed the triggers responsible for moving file attachments in the US, EU, and AU regions, preventing newly uploaded files from being immediately available for download. ### **Resolution** We corrected the issue by restoring the missing triggers and applying the necessary changes. Additionally, any affected files were successfully moved to their intended locations. ### **Impact & Mitigation** * No data loss occurred. * All impacted files were successfully resolved by our corrections. * We corrected the issue to prevent similar discrepancies in future infrastructure changes. We apologize for any inconvenience and appreciate your patience while we resolved this issue.
Between 5:15PM PST and 5:30PM PST, there were a high number of Vault Login errors.
### **Incident Summary** The Keeper DevOps team was alerted to API errors in the US region. Upon investigation, we identified a high number of database deadlocks affecting performance. To mitigate the immediate impact, we restarted the affected writer instance. ### **Root Cause** Historically, similar issues were linked to specific queries impacting MySQL 8.x updates on the RDS Aurora platform. In this case, we discovered that a utility designed to monitor deadlocks and capture diagnostic data was inadvertently contributing to the problem. A known bug in the MySQL minor version used in production caused our data-gathering query—intended to analyze deadlocks—to trigger additional locking, exacerbating the issue. ### **Resolution & Mitigation** * We promptly disabled the problematic monitoring utility and applied database parameter optimizations in collaboration with the AWS team to enhance performance under peak load. * These changes were fully implemented within 24 hours, and no further excessive row locks have been observed. * Our DBA team is actively working with backend engineers to further optimize write operations for improved performance. * A backend code update with additional optimizations is scheduled for release the week of March 17. We appreciate your patience and will continue to monitor and enhance system performance to prevent similar issues in the future.
We are investigating login errors and our team is currently working on the issue.
We are continuing to investigate this issue.
The issue has been resolved
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.
The issue has been resolved and root cause determined. We will update the postmortem on this issue shortly.
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.