# LDAP Degredation

- Provider: [JumpCloud](https://down.guide/providers/jumpcloud)
- Confidence: Confirmed
- Impact: Operational
- lasted 6h 21m
- started 2025-10-05 10:00 UTC
- LDAP - US Region
- us
- id: DWN-14332a551a
- Official page: https://stspg.io/lsw0xn2b8kqd

## Updates from JumpCloud
### 2025-10-05 10:00 UTC: investigating
Currently investigating LDAP performance degradation.

### 2025-10-05 14:29 UTC: 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.

### 2025-10-05 15:35 UTC: 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.

### 2025-10-05 15:54 UTC: identified
We are currently seeing recovery in the LDAP service. We will continue to monitor this situation.

### 2025-10-05 16:21 UTC: resolved
This incident has been resolved.

### 2025-10-08 14:41 UTC: postmortem
!\[\](https://jumpcloud.com/wp-content/themes/jumpcloud/assets/images/jumpcloud-press-kit/logos/01-jc-oceanblue-tm.png)
‌
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

From the builder: does your app depend on JumpCloud? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=jumpcloud) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention JumpCloud.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-14332a551a), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.