- Level
- confirmed
- Worst impact
- Degraded
- Components
- LDAP - US Region
- Regions
- us
- Down Index
- 26of 100
What to do
Check whether you use JumpCloud LDAP - US Region in us. 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 6h 21m it lasted.
Anything that failed between 2025-10-05 10:00 UTC and 2025-10-05 16:21 UTC may need a replay.Subscribe to JumpCloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=jumpcloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from JumpCloud 6
- investigating
Currently investigating LDAP performance degradation.
provider
- investigating
We are currently investigating failures to authenticate using LDAP. We are investigating the cause of the issues currently, and will provide an update within one hour.
provider
- identified
We are continuing to investigate failures to authenticate using LDAP. We have found the cause of the issue and are working to resolve the situation. We will provide an update within one hour.
provider
- identified
We are currently seeing recovery in the LDAP service. We will continue to monitor this situation.
provider
- resolved
This incident has been resolved.
provider
- postmortem
 **Date**: Oct 8, 2025 **Date of Incident:** Oct 5, 2025 **Description**: RCA for LDAP authentication failures **Summary:** On October 5, 2025, a number of customers experienced intermittent failures when attempting to authenticate to LDAP. Users and services attempting to authenticate received an error message indicating a failure to successfully establish a connection. **Root Cause:** The incident was caused by a failure in our automated certificate renewal process. 1. Certificate Expiration: A critical internal Transport Layer Security certificate, used for secure communication within our infrastructure, expired. 2. Automation Failure: The automated system responsible for proactively renewing this certificate failed to run its scheduled update. 3. Cascading Affect: Because the core certificate was not renewed, dependent LDAP services could not renew their own certificates, leading to connection failures with our core database and security vault. The team manually executed the renewal script to update and deploy the expired certificate across all necessary servers, and restarted services on systems that did not pick up the new certificates immediately, restoring normal operation to the LDAP services. **Corrective Actions / Risk Mitigation:** 1. Immediately execute the renewal script and restart services - DONE 2. Implementing dedicated, proactive alerting on the expiration dates of these infrastructure certificates - IN PROGRESS. 3. Add automation checks that verifies the successful execution of the certificate renewal process - IN PROGRESS
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-14332a551a
Is JumpCloud still down?
No, this incident was resolved 2025-10-05 16:21 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.
How long did it last?
6h 21m, from 2025-10-05 10:00 UTC to 2025-10-05 16:21 UTC, by the times JumpCloud posted.
What was affected?
JumpCloud named LDAP - US Region in us.
What caused it?
JumpCloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
JumpCloud's official status page, https://status.jumpcloud.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.