Operational JumpCloud status
jumpcloud.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread JumpCloud problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Google Cloud: no issues
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Admin Console - US Region, User Console - US Region, Admin Console - EU Region
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 21 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: postmortem on “Degraded User and Admin portal”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside JumpCloud's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “postmortem”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
JumpCloud may run on Google Cloud (inferred). We don't map other services that depend on JumpCloud. Dependency chains are where single points of failure hide.
Identity & trust lens
When JumpCloud has trouble, people see failed logins, MFA prompts that don't arrive and sessions that drop. That's when phishing pages and “verify your account” texts show up. Only sign in through the official app or site, and don't re-enter credentials from a link someone sends you.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on JumpCloud or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers JumpCloud may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with JumpCloud. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Degraded User and Admin portal
minor postmortem · started · resolved
4 updates
- investigating
We are currently investigating this issue.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
- postmortem
 **Date of Incident:** Oct 30, 2026\(UTC\) **Description**: Admin Portal and User Portal requests intermittently failed after an internal infrastructure upgrade **Region:** Mostly North America \(Eastern US\). Customers in Europe and Asia-Pacific were also affected, at lower volume **Summary:** Between 04:43 and 06:01 UTC on October 30, 2026, some JumpCloud Admin Portal and User Portal requests failed with server errors. Most of the impact was in our North America region between 05:10 and 06:01 UTC. Affected admins and users saw errors or incomplete pages when viewing devices, device command results, user portal pages and other console pages. Some admin sign-ins, Windows MDM operations and device agent requests also failed. The cause was an upgrade to an internal service that s
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.