- Level
- confirmed
- Worst impact
- Degraded
- Components
- LDAP - US Region
- Regions
- us
- Down Index
- 21of 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 47m it lasted.
Anything that failed between 2026-04-02 17:08 UTC and 2026-04-02 17:55 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 4
- investigating
We are currently investigating a delay in LDAP directory synchronizations. While updates are processing, changes to user attributes and passwords may take longer than expected to propagate. The team is actively working to increase processing capacity and accelerate synchronizations.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
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-80f41a3e64
Is JumpCloud still down?
No, this incident was resolved 2026-04-02 17:55 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.
How long did it last?
47m, from 2026-04-02 17:08 UTC to 2026-04-02 17:55 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.