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, Admin Console - EU Region, Admin Console - IN Region
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 28 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 “Increased error rates loading 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
Increased error rates loading User and Admin portal
major postmortem · started · resolved
6 updates
- investigating
We are currently investigating reports of errors when loading the JumpCloud User or Admin Portal. We will update with additional information within 30 minutes.
- monitoring
We identified errors related to a third party service. Error rates have decreased and we are continuing to monitor.
- monitoring
We are continuing to monitor for any further issues.
- monitoring
Between approximately 15:20 and 15:50 UTC on October 23, 2026, some customers were unable to reliably load the JumpCloud Admin Portal and User Portal. Affected users may have seen error pages or slow, incomplete page loads. The cause was a network disruption at one of our third-party content delivery and security providers, which affected traffic through some of their Eastern US locations. Once their network stabilized, access to both portals returned to normal, and we have confirmed that the issue has been fully resolved. We know how much you depend on reliable access to JumpCloud to manage your organization, and we’re sorry for the disruption this caused you and your users. Even when a disruption starts with a provider, keeping you connected is our responsibility. We already have redundancy in place for this kind of event, and we are actively strengthening it so that failover happens f
- resolved
This incident has been resolved.
- postmortem
 **Date of Incident:** Oct 23, 2026 **Description**: Admin Portal and User Portal intermittently unavailable due to a third-party network disruption **Region:** North America \(Eastern US\). Some users outside the US whose traffic was routed through the affected Eastern US network locations were also impacted. **Summary:** Between approximately 15:21 and 15:46 UTC on October 23, 2026, some customers could not reliably load the JumpCloud Admin Portal and User Portal. Affected users saw error pages or slow, incomplete page loads. The cause was a network disruption at one of our third-party content delivery and security providers. A connectivity failure in their Eastern US network caused congestion and packet loss. Access to both portals returned to normal once the provider’s network
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.