- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Active Directory Integration - US Region
- Regions
- us
- Down Index
- 37of 100
What to do
Check whether you use JumpCloud Active Directory Integration - 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 13h 36m it lasted.
Anything that failed between 2025-05-02 08:52 UTC and 2025-05-02 22:28 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 11
- investigating
We are investigating reports of user accounts being changed to pending status for tenants integrated with Active Directory Bridge.
provider
- investigating
We are continuing to investigate reports of user accounts being changed to pending status for tenants integrated with Active Directory Bridge. We will share another update in one hour.
provider
- identified
We have identified the cause of the issue and a fix is being implemented. We will share another update in one hour.
provider
- identified
We have identified the cause of the issue and are refining the fix to be implemented. We will share another update in one hour.
provider
- identified
We have reverted the update which caused the initial impact. There should be no new occurrences. We are creating a remediation plan at this time and will share it as soon as it is ready. We will share another update in one hour.
provider
- identified
We are in the process of validating our remediation plan. We will communicate it as soon as it is ready. We will share another update in one hour.
provider
- identified
We have identified a fix for this issue. We have validated our remediation plan and are implementing it now. The plan will take several hours to complete. We will provide another update in one hour.
provider
- identified
We are continuing with our implementation of our remediation plan. We anticipate several more hours to complete. We will provide another update in two hours.
provider
- monitoring
We have completed implementation of our remediation plan and do not anticipate any further impact. We will continue to monitor for any issues.
provider
- resolved
This incident has been resolved.
provider
- postmortem
 # **Incident Report** **Date**: May 12, 2025 **Date of Incident:** May 2, 2025 **Description**: RCA for ADI User Login Errors **Summary:** On May 2nd, at approximately 07:00 UTC, a change was deployed to JumpCloud’s Active Directory Integration causing a warning message to appear and preventing successful logins for some users across a subset of organizations. During that time the workaround for users was to change their password, which then allowed a successful login. **Root Cause:** The change introduced was part of an effort to modernize external user identification in Active Directory, which inadvertently caused an error in handling some restricted attributes. This resulted in the incorrect transformation of these fields, setting the password status of some external user accounts to "pending”. This event disrupted user access and necessitated a password update for the affected users until JumpCloud successfully rectified their account status. How was this missed in your testing? Unfortunately, the change affected a subset of users that had a unique combination of values set on their user record. Specifically, the logic was only applied to users that had an empty value on their restricted fields. The testing that was performed did not contain a user in that state, incorrectly passing the test. **Corrective Actions / Risk Mitigation:** 1. Revert that code version - DONE 2. Modify all incorrect user entries in our backend systems - DONE 3. Increased testing scenarios verifying all user states and backward compatibility - 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-7c92be6c83
Is JumpCloud still down?
No, this incident was resolved 2025-05-02 22:28 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.
How long did it last?
13h 36m, from 2025-05-02 08:52 UTC to 2025-05-02 22:28 UTC, by the times JumpCloud posted.
What was affected?
JumpCloud named Active Directory Integration - 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.