- Level
- confirmed
- Worst impact
- Degraded
- Components
- LDAP - US Region, User Console - US Region, SSO - US Region
- Regions
- us
- Down Index
- 17of 100
What to do
Check whether you use JumpCloud LDAP - US Region, User Console - US Region, SSO - 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 10m it lasted.
Anything that failed between 2025-04-30 13:05 UTC and 2025-04-30 13:15 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 3
- monitoring
We have identified an issue that was affecting authentication and SSO and have implemented a fix. Services have recovered and we are monitoring.
provider
- resolved
This incident has been resolved.
provider
- postmortem
 # Incident Report **Date**: May 5, 2025 **Date of Incident:** Apr 30, 2025 **Description**: RCA for User Portal / SSO Failed Authentication **Summary:** On April 30th at 12:35 UTC our monitors detected a significant increase in errors across our User Console API endpoints. The increased errors manifested as failed authentication for new attempts to the User Portal, SSO and other services. Existing connections to applications continued uninterrupted. At 12:41 UTC a formal incident was declared and multiple teams were paged. The issue was resolved at 12:58 UTC **Root Cause:** A state transition anomaly occurred during the credential rotation process for a database within our authentication infrastructure, resulting in connection failures by dependent services to that layer. Consequently, end-users experienced authentication errors when attempting to establish new sessions with specific applications. The authentication service team was able to identify a failure with secondary credentials during the rotation and quickly failed back to valid secrets. **Corrective Actions / Risk Mitigation:** 1. Fail back to primary secrets - DONE 2. Increased automation for secrets rotation at this layer - 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-0b0fc5ccf1
Is JumpCloud still down?
No, this incident was resolved 2025-04-30 13:15 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.
How long did it last?
10m, from 2025-04-30 13:05 UTC to 2025-04-30 13:15 UTC, by the times JumpCloud posted.
What was affected?
JumpCloud named LDAP - US Region, User Console - US Region, SSO - 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.