- Level
- confirmed
- Worst impact
- Partial outage
- Components
- LDAP - US Region
- Regions
- us
- Down Index
- 33of 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 1h 59m it lasted.
Anything that failed between 2025-08-09 06:44 UTC and 2025-08-09 08:43 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 5
- investigating
We are currently investigating reports of an accessibility outage with JumpCloud's LDAP-as-a-Service, and will update the status as more information becomes available.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We are continuing to work on implementing a fix for this issue.
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-cb0a27b1bf
Is JumpCloud still down?
No, this incident was resolved 2025-08-09 08:43 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.
How long did it last?
1h 59m, from 2025-08-09 06:44 UTC to 2025-08-09 08:43 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.