- Level
- confirmed
- Worst impact
- Degraded
- Components
- Admin Console - US Region
- Regions
- us
- Down Index
- 22of 100
What to do
Check whether you use JumpCloud Admin Console - 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 6m it lasted.
Anything that failed between 2025-07-28 12:35 UTC and 2025-07-28 13:41 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 6
- investigating
We're currently investigating reports of an accessibility outage with JumpCloud's Console Service for Administrators at https://console.jumpcloud.com/. We will be providing an update within the next 30 minutes.
provider
- investigating
The issue has been narrowed down to affect only Admins linked to a User Account. Non user-linked Admin accounts should be able to access the console successfully. We continue to investigate.
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
- postmortem
 # **Incident Report** **Date**: Jul 30, 2025 **Date of Incident:** Jul 28, 2025 **Description**: RCA for linked User-Admin account login failures to the Admin Portal **Summary:** On July 28th at approximately 12:30 UTC \(**UPDATE:** 11:00 UTC\), some administrators linked to user accounts experienced an inability to log in to the JumpCloud Admin Portal. The issue manifested as a redirection to an internal error during the login flow. **Root Cause:** The incident originated during a planned system enhancement, specifically an upgrade to a core database interaction library. An unintended software error was introduced into our web interface during this update. A specific component of our login process, responsible for handling admin authentication, was updated to receive a confirmation or next step instruction \(a 'callback'\) after completing its task. However, in one particular login pathway, this instruction was not provided as expected and the missing instruction caused the system to error, and incorrectly redirect affected administrators with linked user accounts to a generic error page instead of completing their login. **Corrective Actions / Risk Mitigation:** 1. Immediately revert the affected web UI component to its previous stable version in our production environments - DONE 2. Implement additional automated and manual testing and validation steps, particularly for critical login and database interaction code - IN PROGRESS 3. Reinforce checks to ensure all refactored code paths explicitly handle expected responses and potential error conditions - DONE 4. Implement additional monitoring specifically designed to detect similar anomalies in login flows proactively - 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-63c9fa5e81
Is JumpCloud still down?
No, this incident was resolved 2025-07-28 13:41 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.
How long did it last?
1h 6m, from 2025-07-28 12:35 UTC to 2025-07-28 13:41 UTC, by the times JumpCloud posted.
What was affected?
JumpCloud named Admin Console - 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.