- Level
- confirmed
- Worst impact
- Degraded
- Components
- Windows MDM - US Region
- Regions
- us
- Down Index
- 26of 100
What to do
Check whether you use JumpCloud Windows MDM - 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 6h 33m it lasted.
Anything that failed between 2025-09-10 14:15 UTC and 2025-09-10 20:48 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 9
- investigating
We are currently investigating an issue involving JumpCloud’s Windows MDM Service that is preventing device enrollment. We are investigating the cause of the issues currently, and will update the status event once an update is available.
provider
- identified
We have identified the issue and are working on a fix.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We're still implementing a fix for this issue. We will provide another update within the hour.
provider
- identified
We are still working to implement a fix for this issue. We will continue providing regular updates.
provider
- identified
We are continuing to work to implement a fix for this issue. During this time new Windows MDM device enrollments will continue to fail.
provider
- monitoring
A fix has been implemented and we are continuing to monitor the results.
provider
- resolved
This issue has been resolved and Windows devices are now able to successfully enroll in MDM.
provider
- postmortem
 # Incident Report **Date**: Sep 13, 2025 **Date of Incident:** Sep 10, 2025 **Description**: **RCA for Windows MDM enrollment failures** **Summary:** On September 10, 2025, a number of customers experienced intermittent failures when attempting to enroll Windows MDM devices. User-led enrollments during this period would have seen an error message. **Root Cause:** Our MDM team was alerted to an issue with our MDM certificate issuance service, which affected the ability to enroll devices. This issue was caused by a configuration change in our backend infrastructure. The core problem stemmed from an update that inadvertently caused a critical service role to be deleted and immediately recreated. When this happened, our IaaS provider assigned the recreated role a new, unique ID. Our system, which was configured to recognize the old ID, was no longer able to access the necessary security keys. This caused certificate issuance to fail, causing the MDM enrollment failures. **Corrective Actions / Risk Mitigation:** 1. Implemented a permanent fix refactoring our infrastructure for this service - DONE 2. Refining our emergency response plan to securely restore services - IN PROGRESS 3. Updating our monitoring systems to proactively detect and alert on these types of issues, including reconfiguring our logging to ensure that critical errors are not missed - 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-5439450633
Is JumpCloud still down?
No, this incident was resolved 2025-09-10 20:48 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.
How long did it last?
6h 33m, from 2025-09-10 14:15 UTC to 2025-09-10 20:48 UTC, by the times JumpCloud posted.
What was affected?
JumpCloud named Windows MDM - 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.