Skip to main content
JumpCloud

Admin Portal Access Issues

Partial outage Lasted 0m · started · JumpCloud's page

Level
confirmed
Worst impact
Partial outage
Down Index
18of 100

What to do

  • Check whether your product depends on JumpCloud. 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 0m it lasted.

    Anything that failed between 2025-09-15 07:55 UTC and 2025-09-15 07: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 2

  1. resolved

    There were issues with the following services; Admin Portal & Mobile Admin App Login & Direct API calls. This is resolved now.

    provider

  2. postmortem

    ![](https://jumpcloud.com/wp-content/themes/jumpcloud/assets/images/jumpcloud-press-kit/logos/01-jc-oceanblue-tm.png) # **Incident Report**  ‌ **Date**: Sep 15, 2025 **Date of Incident:** Sep 16, 2025 **Description**: RCA for Admin Portal Access Failures ‌ **Summary:** On September 15, 2025, between 08:59 UTC - 09:11 UTC customers experienced failures when attempting to access the Admin Portal.  Users and services attempting to authenticate received a loading error message during that window. ‌ **Root Cause:** The incident originated during an update to support a new API for our SaaS Management Service. The update was designed to allow a new console subdomain to handle traffic, in addition to the existing SaaS subdomain. ‌ While this change successfully passed all testing in our pre-production environment, our automated deployment system failed to apply the full configuration in production. It applied the new console subdomain but, due to a misconfiguration, it omitted a critical path prefix. This resulted in an issue where traffic intended for a different service was routed incorrectly, causing a brief service outage. ‌ As soon as the errors appeared, the team immediately rolled back the change, and service was restored. We have identified the root cause in our automated deployment process and are implementing a fix to prevent this from happening again.

    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-0e4a1f5ccf

Is JumpCloud still down?

No, this incident was resolved 2025-09-15 07:55 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.

How long did it last?

0m, from 2025-09-15 07:55 UTC to 2025-09-15 07:55 UTC, by the times JumpCloud posted.

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.