Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for JumpCloud and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for JumpCloud.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Active Directory Integration | Active |
Admin Console | Active |
Agent | Active |
Android EMM | Active |
Commands | Active |
Directory Insights | Active |
Federation | Active |
General Access API | Active |
G Suite Integration | Active |
JumpCloud GO | Active |
JumpCloud University | Active |
LDAP | Active |
MDM | Active |
Mobile Admin App: iOS and Android | Active |
Multi-Tenant Portal (MTP) | Active |
Office 365 Integration | Active |
Password Manager | Active |
Payment and Billing | Active |
Policy Management | Active |
RADIUS | Active |
Remote Assist | Active |
SCIM | Active |
Self-Service Account Provisioning (Devices SSAP) | Active |
Software Management | Active |
SSO | Active |
SSO | Maintenance |
System Insights | Active |
TOTP / MFA / JumpCloud Protect | Active |
User Console | Active |
User Import from CSV | Active |
Workday Import | Active |
www.jumpcloud.com | Active |
Cloudflare | Active |
Cloudflare CDN/Cache | Active |
Cloudflare Cloudflare Firewall | Active |
Security | Active |
Security Advisories | Active |
Security Notifications | Active |
Support Services | Active |
Email Support | Active |
jumpcloud.com/support | Active |
Premium Chat Support | Active |
Premium Phone Support | Active |
View the latest incidents for JumpCloud and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Jan. 16, 2024, 4:09 p.m.
Description: This issue is resolved. Some customers may need to log out and back in the User Console for all SSO applications to authenticate correctly.
Status: Resolved
Impact: Minor | Started At: Jan. 15, 2024, 6:48 p.m.
Description: # **JumpCloud Incident Report** **Date**: 2023-12-20 **Date of Incident**: 2023-12-18 **Description**: RCA for Admin Portal Login with MFA **Summary:** At 08:26 MST on 2023-12-18, some JumpCloud customers experienced failures while authenticating to JumpCloud’s Admin console using MFA. Two additional issues were present during this time. First, any password update for users would fail to complete. Second, if a user or admin tried to change their TOTP, subsequent attempts to sign-in with that TOTP would fail. This degradation of service lasted until 09:49 MST on 2023-12-18. Admins that attempted a TOTP reset during the incident did experience lingering issues requiring further intervention. **Root Cause:** At JumpCloud we extensively use the [principle of least privilege \(PoLP\)](https://en.wikipedia.org/wiki/Principle_of_least_privilege). To accomplish this, our services use IAM policies to access only the resources they need to successfully fulfill requests. To manage those IAM policies we use [Infrastructure as Code \(IaC\)](https://en.wikipedia.org/wiki/Infrastructure_as_code) to ensure the policies have the proper reviews before getting merged into our git repositories and released. Our release pipelines allow us to validate and test IAM policy changes in our pre-production environment before applying the changes to production. During the validation step we run what is called a speculative plan, which shows us what the changes are going to look like so the team can do a final review without having to apply the changes. On December 18th at 08:07 MT the plan for the production policy change ran successfully showing us what the policy would look like. But, due to differences in the test application and the production application the size of the IAM policy differed, and because we did not have any test to check the policy size all tests were passing. At 08:26 MT the team moved forward to apply the changes to the production service. Most policy changes applied without issue, but one policy exceeded the character limit and failed. This caused the service to be unable to reach the required resources needed to fulfill its requests. At 08:32 MT the team was alerted to elevated failure rates on the admin login window and began investigating. At 08:52 MT the team identified the problematic policy and attempted to fix it and roll forward. Unfortunately the fix was unsuccessful and the team pivoted to roll the change back. The rollback completed at 09:47 MT and service was restored. One side-effect of this incident was that if updates to TOTP devices were made, our service failed in an unexpected way. End user devices showed the new TOTP, but our backend was unable to actually save that change. This caused users who made updates during the incident window to fail subsequent logins using their new TOTP. This failure mode was not apparent to the team investigating the incident, so no updates to our status page were made. **Corrective Actions / Risk Mitigation:** 1. Revert the offending policy change - DONE 2. Introduce a manual stop-gap process until action 4 is completed. - DONE 3. Process updated for Statuspage requiring additional communication on any possible lingering effects - DONE 4. Additional automated safeguards for changes to managed policies - TARGET 01/2024 5. Fix failure mode to prevent unexpected password or device state - IN REVIEW
Status: Postmortem
Impact: Minor | Started At: Dec. 18, 2023, 3:54 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Dec. 13, 2023, 2:47 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Dec. 4, 2023, 10:40 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.