- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Keeper. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-07-06 15:00 UTC and 2025-07-06 15:00 UTC may need a replay.Subscribe to Keeper's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=keeper works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Keeper 2
- resolved
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.
provider
- postmortem
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-607c054260
Is Keeper still down?
No, this incident was resolved 2025-07-06 15:00 UTC. For Keeper's live state, see https://down.guide/keeper.
How long did it last?
0m, from 2025-07-06 15:00 UTC to 2025-07-06 15:00 UTC, by the times Keeper posted.
What caused it?
Keeper hasn't published a root cause. If it does, it shows here.
Where does this come from?
Keeper's official status page, https://statuspage.keeper.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.