JumpCloud

Affected: Commands - US Region, Commands - EU Region, Commands - IN Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-25 17:27 UTC

   We're currently investigating reports of degraded performance with updating Details or Associations to Commands in the Admin Portal. We are investigating the cause of the issues currently, and will update the status event once resolved.

2. identified 2026-09-25 17:29 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-25 17:55 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-25 18:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: RADIUS - EU Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-14 13:25 UTC

   We are currently investigating an issue where after a password reset, some RADIUS sign-ins (VPN/Wi‑Fi) may fail with the new password. However - impacted users can still login with old password. We are investigating the cause of the issues currently, and will provide an update...

2. monitoring 2026-09-14 13:58 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-14 14:38 UTC

   This incident has now been resolved.

4. postmortem 2026-09-21 20:49 UTC

    # **Incident Report** **Date**: Sep 21, 2026 **Date of Incident:** Sep 14, 2026 **Description**: Root Cause Analysis for RADIUS authentication failures affecting EU users...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Groups (user/devices) - US Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 06:07 UTC

   JumpCloud is currently experiencing delays in assigning Users and Systems to Dynamic Groups. Administrators may see delays in these Group membership updates, and thus delays in provisioning to connected resources.

2. identified 2026-09-03 06:14 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-09-03 08:56 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2026-09-03 10:05 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2026-09-03 10:54 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-09-03 12:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: User Console - US Region

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-06-22 14:21 UTC

   We are currently investigating delays or timeouts loading the user console. We are investigating the cause of the issues currently, and will provide an update within one hour.

2. identified 2026-06-22 15:08 UTC

   We have identified that a third party outage is impacting our service. More information can be found at https://www.cloudflarestatus.com/incidents/v3yl7jqmqj51

3. resolved 2026-06-22 16:39 UTC

   The third party issue impacting our service has been resolved. Our internal monitoring is showing service states returned to normal.

4. postmortem 2026-06-25 20:00 UTC

    ‌ **Date**: Jun 25, 2026 **Date of Incident:** Jun 22, 2026 **Description**: RCA for Third-Party CDN Network Disruption — Cloudflare / Zayo Fiber Cut ‌ #### **Summary:** On...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-08 06:41 UTC

   We are currently investigating delays or timeouts loading the devices page in the admin console. We are investigating the cause of the issues currently, and will provide an update within one hour.

2. identified 2026-05-08 06:44 UTC

   The issue has been identified and the team is working on the fix.

3. monitoring 2026-05-08 06:51 UTC

   A fix has been implemented. We are currently monitoring the results.

4. resolved 2026-05-08 08:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Agent - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-28 08:01 UTC

   We are currently aware of reports with agent Installation failing, this is affecting MacOS, Windows and Linux. We are investigating the cause of the issues currently, and will provide an update within one hour.

2. identified 2026-04-28 08:57 UTC

   The issue has been identified and a fix will be implemented soon.

3. monitoring 2026-04-28 09:00 UTC

   A fix has been implemented, and Agent installations should now be functioning as expected. Our team is actively monitoring the situation to ensure continued stability.

4. resolved 2026-04-28 09:55 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: LDAP - US Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-02 17:08 UTC

   We are currently investigating a delay in LDAP directory synchronizations. While updates are processing, changes to user attributes and passwords may take longer than expected to propagate. The team is actively working to increase processing capacity and accelerate...

2. identified 2026-04-02 17:16 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-02 17:23 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-02 17:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-31 00:32 UTC

   JumpCloud is currently experiencing dispatch delays for core Directory services. Administrators may experience delays updating associations for users, groups, policies, directories, and commands. We have identified the cause of the issue and are actively implementing a fix.

2. identified 2026-03-31 02:38 UTC

   We have made progress in reducing the backlog affecting Directory services and are continuing to work through the remaining queue. Administrators may still experience delays when updating associations for users, groups, policies, directories, and commands. The team is actively...

3. identified 2026-03-31 03:42 UTC

   The backlog affecting Directory services has been significantly reduced and continues to decrease. Administrators may still experience delays when updating associations for users, groups, policies, directories, and commands. The team continues to work on additional changes to...

4. monitoring 2026-03-31 05:00 UTC

   The backlog affecting Directory services continues to decrease and we are approaching resolution. Administrators may still experience some delays when updating associations. The team is continuing to monitor, and our next update will be to confirm full resolution.

5. resolved 2026-03-31 06:24 UTC

   This incident has been resolved.

6. postmortem 2026-04-07 14:56 UTC

    **Date**: Apr 7, 2026 **Date of Incident:** Mar 30, 2026 **Description**: RCA for Directory Association Processing Delays ‌ **Summary:** Starting March 30th at...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Agent - US Region

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-12 16:54 UTC

   We are currently investigating an issue with delays in syncing user, commands, and policy information with the JumpCloud Devices Agent backend service. We are investigating the cause of the issues currently, and will provide an update within one hour. Agent / Device logins are...

2. investigating 2026-03-12 18:08 UTC

   We are continuing to investigate an issue with delays in syncing user, commands, and policy information with the JumpCloud Devices Agent backend service. Local Agent / Device logins without MFA or leveraging TOTP are operating as expected.

3. investigating 2026-03-12 19:24 UTC

   We are continuing to investigate an issue with delays in syncing user, commands, and policy information with the JumpCloud Devices Agent backend service. Local Agent / Device logins without MFA or leveraging TOTP are operating as expected.

4. identified 2026-03-12 20:26 UTC

   The issue has been identified and we have implemented a fix. We are starting to see some recovery with many agents checking in. We will update as our agent traffic normalizes.

5. monitoring 2026-03-12 21:08 UTC

   Agent traffic is reaching normal levels, and the majority of customers are seeing full service restoration. Our engineering teams continue to actively monitor backend stability and traffic patterns. We expect to move to 'Resolved' status shortly as final systems stabilize.

6. resolved 2026-03-12 21:48 UTC

   This incident has been resolved.

7. postmortem 2026-03-17 21:25 UTC

    ‌ **Date**: Mar 17, 2026 **Date of...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Cloudflare CDN/Cache

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-21 12:34 UTC

   We had reports of delays or timeouts when accessing the Admin and User Portal consoles but now recovering. This issue has been traced to an ongoing network problem within the Asia region reported by Cloudflare. We are closely monitoring the situation and will provide an update...

2. monitoring 2025-11-21 12:44 UTC

   Per the latest update from CloudFlare, a fix has been implemented and results are being monitored. https://www.cloudflarestatus.com/incidents/5p8c3l54b5cl

3. resolved 2025-11-21 14:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-19 06:46 UTC

   We're currently investigating reports of intermittent access issues with JumpCloud's Console Service for administrator at https://console.jumpcloud.com/. We are investigating the cause of the issues currently, and will update the status event once resolved.

2. monitoring 2025-11-19 07:00 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-11-19 07:16 UTC

   Issue is resolved and closed.

4. postmortem 2025-11-21 18:25 UTC

    ‌ **Date**: Nov 21, 2025 **Date of Incident:** Nov 19, 2025 **Description**: RCA for Admin Portal Login Errors ‌ **Summary:** On November 19, 2025, starting at...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Remote Assist - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-11 08:17 UTC

   We are currently investigating reports of intermittent issues with launching Remote Assist tool. We are investigating the cause of the issue currently, and will provide an update within one hour.

2. identified 2025-11-11 08:40 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-11-11 09:12 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-11 09:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: SSO OIDC - US Region

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-06 12:28 UTC

   We are currently investigating an issue with the authentication on SSO OIDC applications. We have already identified the cause and will provide an update within one hour.

2. identified 2025-11-06 12:33 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-11-06 13:10 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-06 13:47 UTC

   This incident has been resolved.

5. postmortem 2025-11-13 23:33 UTC

    ‌ **Date**: Nov 13, 2025 **Date of Incident:** Nov 6, 2025 **Description**: RCA for SSO/OIDC Service Degradation ‌ **Summary:** On November 6, 2025, starting at...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region, LDAP - US Region, RADIUS - US Region, User Console - US Region, TOTP / MFA / JumpCloud Protect - US Region, SSO - US Region

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-04 11:40 UTC

   We are seeing issues with SSO authentication. We are investigating this currently and will update within 1 hour

2. investigating 2025-11-04 11:41 UTC

   We are continuing to investigate this issue.

3. investigating 2025-11-04 11:47 UTC

   We are continuing to investigate this issue.

4. identified 2025-11-04 12:20 UTC

   We have identified an issue that is causing intermittent login issues with the JumpCloud User Portal and Admin Portal. We have also identified issues with JumpCloud MFA, LDAP, RADIUS, and authentication with SSO. We are working on implementing a fix and will provide another...

5. identified 2025-11-04 12:59 UTC

   We continue to see intermittent issues with accessing the JumpCloud User and Admin Portal, MFA, LDAP, RADIUS, and SSO. During this time access attempts to LDAP and RADIUS are only impacted if a user is authenticating with MFA. Our team is working on implementing a fix and will...

6. monitoring 2025-11-04 13:17 UTC

   We have implemented a fix and users should now be able to access the User and Admin Console, MFA, LDAP, RADIUS, and SSO without issue. We will continue to monitor the results of the fix.

7. resolved 2025-11-04 14:19 UTC

   Services have been fully restored and this incident has been resolved. We will provide a formal postmortem as a follow up.

8. postmortem 2025-11-07 17:47 UTC

    ‌ **Date**: Nov 7, 2025 **Date of Incident:** Nov 4, 2025 **Description**: RCA for Auth Database Degradation ‌ **Summary:** On November 4, 2025, a number of...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Privileged Access Management (PAM) - US Region, Premium Chat Support

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 15:44 UTC

   Due to an issue with our Cloud Provider, JumpCloud is experiencing intermittent issues with our PAM service and some Support tools which may affect case creation. We are investigating this with our provider and will update this incident as we know more.

2. identified 2025-10-20 15:50 UTC

   We are monitoring our services and continue to work with our provider to restore full functionality.

3. monitoring 2025-10-20 17:43 UTC

   We've seen an increase in recovery and are monitoring

4. resolved 2025-10-20 21:46 UTC

   This incident has been resolved.

5. postmortem 2025-10-27 19:21 UTC

    **Date**: Oct 27, 2025 **Date of Incident:** Oct 20, 2025 **Description**: RCA for Service Degradation Linked to AWS US-EAST-1 Regional Disruption ‌ **Summary:**...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region, User Console - US Region, Admin Console - EU Region, User Console - EU Region

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:52 UTC

   Due to an issue with our Cloud Provider, JumpCloud is experiencing intermittent issues with multiple services. We are investigating this with our provider and will update this incident as we know more.

2. identified 2025-10-20 09:11 UTC

   We are monitoring our services, and starting to see some recovery.

3. monitoring 2025-10-20 10:02 UTC

   We are continuing to monitor as we see further recovery with all services.

4. resolved 2025-10-20 10:14 UTC

   This incident has been resolved.

5. postmortem 2025-10-27 19:18 UTC

    **Date**: Oct 27, 2025 **Date of Incident:** Oct 20, 2025 **Description**: RCA for Service Degradation Linked to AWS US-EAST-1 Regional Disruption ‌ **Summary:**...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: www.jumpcloud.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-14 08:52 UTC

   We are currently investigating an issue, where navigating links (specifically redirects) at the JumpCloud website are affected. We are suspecting an ongoing "Bot Management Cookie" incident declared by CloudFlare to be at the root. More details can be found at...

2. identified 2025-10-14 08:59 UTC

   CloudFlare has identified the issue and is implementing a fix. We are monitoring https://www.cloudflarestatus.com for updates.

3. identified 2025-10-14 12:51 UTC

   CloudFlare continues to work on the issue and we are monitoring their status page at https://www.cloudflarestatus.com

4. identified 2025-10-14 13:34 UTC

   CloudFlare continues to work on the issue and we are monitoring their status page at https://www.cloudflarestatus.com

5. monitoring 2025-10-14 14:12 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2025-10-14 14:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Remote Assist - US Region, Remote Assist - EU Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-09 14:20 UTC

   We are currently investigating an issue where the Remote Assist and Background tools actions are unavailable in the Admin Console.

2. investigating 2025-10-09 14:22 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-10-09 14:32 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-10-09 14:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-07 09:32 UTC

   We are investigating slow performance with the Admin Portal. We will update within an hour.

2. monitoring 2025-10-07 11:08 UTC

   Our investigation uncovered intermittent latencies at several end-points which caused slow response times at the Admin portal for a few customers. Out of an abundance of caution, we have rolled back a recent update and will continue monitoring.

3. resolved 2025-10-07 11:23 UTC

   The issue is now marked as resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: LDAP - US Region

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-05 10:00 UTC

   Currently investigating LDAP performance degradation.

2. investigating 2025-10-05 14:29 UTC

   We are currently investigating failures to authenticate using LDAP. We are investigating the cause of the issues currently, and will provide an update within one hour.

3. identified 2025-10-05 15:35 UTC

   We are continuing to investigate failures to authenticate using LDAP. We have found the cause of the issue and are working to resolve the situation. We will provide an update within one hour.

4. identified 2025-10-05 15:54 UTC

   We are currently seeing recovery in the LDAP service. We will continue to monitor this situation.

5. resolved 2025-10-05 16:21 UTC

   This incident has been resolved.

6. postmortem 2025-10-08 14:41 UTC

    ‌ **Date**: Oct 8, 2025 **Date of Incident:** Oct 5, 2025 **Description**: RCA for LDAP authentication failures ‌ **Summary:** On October 5, 2025, a number of...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: System Insights - US Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-18 11:57 UTC

   We are aware of a delay in software inventory data updating. We are currently working on this and aim to update within 1 hour.

2. identified 2025-09-18 13:03 UTC

   We have identified the issue and are applying a fix to resolve this issue. We will update within an hour.

3. identified 2025-09-18 14:07 UTC

   We are still applying the fix. We will update as soon as the delay reduces.

4. monitoring 2025-09-18 14:17 UTC

   The fix has been applied. Software Inventory data is now within the acceptable time range. We will continue to monitor.

5. resolved 2025-09-18 14:35 UTC

   The data is now remaining within the acceptable range. We consider this to be resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-09-15 07:55 UTC

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

2. postmortem 2025-09-16 20:25 UTC

    # **Incident Report** ‌ **Date**: Sep 15, 2025 **Date of Incident:** Sep 16, 2025 **Description**: RCA for Admin Portal Access Failures ‌ **Summary:** On...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Windows MDM - US Region

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-09-10 14:15 UTC

   We are currently investigating an issue involving JumpCloud’s Windows MDM Service that is preventing device enrollment. We are investigating the cause of the issues currently, and will update the status event once an update is available.

2. identified 2025-09-10 14:49 UTC

   We have identified the issue and are working on a fix.

3. identified 2025-09-10 14:57 UTC

   The issue has been identified and a fix is being implemented.

4. identified 2025-09-10 16:09 UTC

   We're still implementing a fix for this issue. We will provide another update within the hour.

5. identified 2025-09-10 17:43 UTC

   We are still working to implement a fix for this issue. We will continue providing regular updates.

6. identified 2025-09-10 19:02 UTC

   We are continuing to work to implement a fix for this issue. During this time new Windows MDM device enrollments will continue to fail.

7. monitoring 2025-09-10 19:55 UTC

   A fix has been implemented and we are continuing to monitor the results.

8. resolved 2025-09-10 20:48 UTC

   This issue has been resolved and Windows devices are now able to successfully enroll in MDM.

9. postmortem 2025-09-12 18:38 UTC

    # Incident Report‌ **Date**: Sep 13, 2025 **Date of Incident:** Sep 10, 2025 **Description**: **RCA for Windows MDM enrollment failures** ‌ **Summary:** On...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Reporting - US Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-04 13:14 UTC

   We are seeing issues with stale data on reports in JumpCloud. We have deployed the relevant fix and will continue to monitor this issue. Please note that data in reports is only affected and all other data is correct. We will update within 1 hour.

2. identified 2025-09-04 14:47 UTC

   We are still working on this issue. We are monitoring the reduction in stale data and will provide a further update in the next few hours.

3. monitoring 2025-09-04 17:24 UTC

   A fix has been implemented and we are currently monitoring the progress in updating the stale data. We will provide further updates in the next two hours.

4. monitoring 2025-09-04 19:21 UTC

   We are still monitoring the progress in updating the stale data. We will continue to provide regular communication. Please expect the another update within the next two hours.

5. resolved 2025-09-04 21:34 UTC

   This incident has been resolved. Reports data is now fully up to date.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region, User Console - US Region

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-28 11:46 UTC

   We're currently investigating reports of an accessibility outage with JumpCloud's Console Service for Admin and user login at https://console.jumpcloud.com/. We are investigating the cause of the issues currently, and will update the status event once resolved.

2. identified 2025-08-28 11:56 UTC

   CloudFlare is reporting Network Performance issues in the Jakarta region. CloudFlare is working to resolve the issue. More information can be found at https://www.cloudflarestatus.com/

3. monitoring 2025-08-28 12:02 UTC

   CloudFlare has implemented a fix and the admin and user consoles are accessible now from the affected region. We are monitoring and will mark this as resolved as soon as CloudFlare confirms resolution.

4. resolved 2025-08-28 12:19 UTC

   This incident is now marked as resolved following the update at CloudFlare status page - https://www.cloudflarestatus.com/ (Past Incidents).

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Directory Insights - US Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-25 17:59 UTC

   We're currently investigating an issue with some Directory, SSO, and Password Manager insights events not propagating. We'll provide an update as soon as we have more information.

2. monitoring 2025-08-25 19:44 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-08-25 19:59 UTC

   This incident has been resolved. The team is working on a data backfill process for missing events from this event, and we expect this to complete in several hours.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Cloudflare CDN/Cache

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. monitoring 2025-08-21 19:16 UTC

   We are monitoring an issue with Cloudflare causing intermittent latency with JumpCloud services. All services are functional, however some customers may experience intermittent latency when accessing the Admin portal or other services. Cloudflare status can be monitored here:...

2. resolved 2025-08-21 20:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: LDAP - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-09 06:44 UTC

   We are currently investigating reports of an accessibility outage with JumpCloud's LDAP-as-a-Service, and will update the status as more information becomes available.

2. identified 2025-08-09 07:31 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-08-09 08:08 UTC

   We are continuing to work on implementing a fix for this issue.

4. monitoring 2025-08-09 08:22 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-08-09 08:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Apple MDM - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-08 13:26 UTC

   We are currently investigating an issue affecting iOS and iPadOS MDM enrollments that utilize Automated Device Enrollment.

2. monitoring 2025-08-08 14:41 UTC

   A fix has been implemented and we are monitoring results.

3. resolved 2025-08-08 14:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-05 09:23 UTC

   We are currently investigating an issue with adding Admin accounts or modifying admin roles. Our team is actively working on this and will supply an update within 1 hour.

2. identified 2025-08-05 09:24 UTC

   We have identified the issue and are working on a fix for this issue. We will provide a further an update within 1 hour.

3. monitoring 2025-08-05 09:59 UTC

   A fix has been implemented and we are monitoring the results. Admins should now be able to create new admin accounts and modify admin roles.

4. monitoring 2025-08-05 10:00 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-08-05 10:14 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: RADIUS - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-29 13:36 UTC

   We're currently investigating reports of intermittent connection issues with JumpCloud's RADIUS-as-a-Service. We are investigating the cause of the issues currently.

2. monitoring 2025-07-29 14:04 UTC

   A fix has been implemented and we are monitoring the results. Users should now be able to authenticate to JumpCloud's RADIUS-as-a-Service.

3. resolved 2025-07-29 14:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-29 07:50 UTC

   We're currently investigating reports of usability issues with JumpCloud's Admin Portal. We are investigating the cause of the issues currently, and will update the status once resolved.

2. monitoring 2025-07-29 08:25 UTC

   The issue has been identified and a fix has been implemented. We are now monitoring the results. The Admin Portal is fully operational now.

3. resolved 2025-07-29 08:38 UTC

   All operations have returned to normal and the issue is currently considered resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-07-28 12:35 UTC

   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.

2. investigating 2025-07-28 12:45 UTC

   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.

3. identified 2025-07-28 13:25 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2025-07-28 13:34 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-07-28 13:41 UTC

   This incident has been resolved.

6. postmortem 2025-07-30 13:57 UTC

    # **Incident Report** ‌ **Date**: Jul 30, 2025 **Date of...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Directory Insights - US Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-24 10:14 UTC

   We're investigating reports of an issue with JumpCloud's Directory Insights Service not populating events in the Admin Portal. We are investigating the cause of the issue currently, and will update the status once resolved.

2. monitoring 2025-07-24 10:36 UTC

   A fix has been implemented and we are monitoring the results. Directory Insights Service is now fully operational.

3. resolved 2025-07-24 10:53 UTC

   A partial outage of JumpCloud's Directory Insight Service not populating events at the Admin Portal, is now resolved All operations have returned to normal, and the issue is currently considered resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: JumpCloud University - US Region

Failure mode: A schema or data migration caused the failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-07-15 17:06 UTC

   university.jumpcloud.com is still under maintenance, and we are currently working with our third party vendor on implementing a fix to resolve the outstanding issues with the migration.

2. resolved 2025-07-15 18:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-15 13:23 UTC

   We are experiencing an intermittent issue when loading the Rules page under Alerts. We are currently investigating this issue and will supply an update shortly.

2. investigating 2025-07-15 14:38 UTC

   We're still investigating the cause of this issue and will follow-up with an update shortly. In the meantime, as this issue is intermittent, continue to refresh the page until it loads successfully.

3. identified 2025-07-15 16:21 UTC

   We have identified the cause of the issue and we are currently working on a fix. We will follow-up once the update has been deployed

4. resolved 2025-07-15 19:45 UTC

   A fix has been deployed and full functionality has been restored.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Custom API Import - US Region

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-14 16:59 UTC

   We are currently experiencing an issue where IDM custom API Import integrations are showing as inactive. The team has determined there is a disconnect between the front end UI and our backend systems. A reconfiguration of the integration is not necessary and should re-activate...

2. identified 2025-07-14 17:00 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-07-14 20:00 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2025-07-14 21:43 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-07-14 21:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: RADIUS - US Region

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-10 05:02 UTC

   We're currently investigating reports of degraded performance or intermittent connection issues with JumpCloud's RADIUS-as-a-Service. We are investigating the cause of the issues currently, and will update the status event once resolved.

2. monitoring 2025-07-10 06:33 UTC

   Our investigations have not uncovered any anomalies with the RADIUS service. While we will continue to monitor, the status of the service is now Operational.

3. resolved 2025-07-10 13:44 UTC

   Earlier reports of service degradation were investigated and no anomalies were found. However, out of an abundance of caution, our Engineering Team has rolled back a recent update to one of the pods in our RADIUS infrastructure. After a period of close monitoring, the status of...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: System Insights - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-30 22:10 UTC

   We are currently investigating an issue impacting System Insights.

2. investigating 2025-06-30 23:06 UTC

   We are still investigating the issue impacting System Insights.

3. identified 2025-07-01 00:15 UTC

   The issue has been identified and a fix is being implemented.

4. resolved 2025-07-01 00:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Directory Insights - US Region, System Insights - US Region, Policy Management - US Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-16 13:38 UTC

   We are currently investigating an issue where device's policy results are not displayed as expected. Policies applied to devices will continue to function as expected during this time.

2. investigating 2025-06-16 14:15 UTC

   We are continuing to investigate an issue where device's policy results are not displayed as expected. Policies applied to devices will continue to function as expected during this time.

3. identified 2025-06-16 15:01 UTC

   The issue has been identified and a fix is being implemented.

4. identified 2025-06-16 15:11 UTC

   The issue has been identified and a fix is being implemented.

5. monitoring 2025-06-16 16:06 UTC

   A fix has been implemented and we are monitoring the results.

6. monitoring 2025-06-16 16:41 UTC

   A fix has been implemented and we are still monitoring the results.

7. resolved 2025-06-16 17:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: RADIUS - US Region

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-10 15:13 UTC

   We're currently investigating reports of issues with JumpCloud's RADIUS-as-a-Service. We are investigating the cause of the issues.

2. identified 2025-06-10 15:20 UTC

   The issue with RADIUS has been identified and we are working on a fix.

3. monitoring 2025-06-10 15:57 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-06-10 16:22 UTC

   This incident has been resolved.

5. postmortem 2025-06-12 20:36 UTC

    # **Incident Report** ‌ **Date**: Jun 12, 2025 **Date of...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Email Support

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-10 05:56 UTC

   We are currently investigating intermittent reports of Administrators being unable to submit support cases via the JumpCloud Admin Portal. Support cases can still be submitted by emailing support@jumpcloud.com. We are investigating the cause of the issues currently, and will...

2. monitoring 2025-06-10 06:10 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-06-10 06:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: System Insights - US Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-05 13:13 UTC

   We are currently investigating an issue with System Insights displaying incorrect Local User Information in the Admin Console. We will report back as soon as we have an update. We apologize for any disruption this may cause. Thank you,

2. investigating 2025-06-05 14:00 UTC

   We are continuing to investigate the issue with System Insights displaying incomplete Local User Information in the Admin Console. We will report back as soon as we have an update. We apologize for any disruption this may cause. Thank you,

3. identified 2025-06-05 14:30 UTC

   We have identified the issue with System Insights displaying incomplete Local User Information in the Admin Console and are currently working on implementing a fix. We will report back as soon as we have any further update.

4. monitoring 2025-06-05 15:08 UTC

   We have implemented the fix for the issue with System Insights displaying incomplete Local User Information in the Admin Console. We will continue to monitor this and once we are sure this is resolved will proceed to resolve the incident.

5. resolved 2025-06-05 15:26 UTC

   This issue has been resolved and service has now returned to normal.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-14 14:22 UTC

   We're currently investigating an issue with JumpCloud's Console where Administrators may be unable to save changes for some device records. We are investigating the cause of the issues currently, and will update the status event once resolved.

2. identified 2025-05-14 14:47 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-05-14 16:24 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-05-14 17:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Active Directory Integration - US Region

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-05-02 08:52 UTC

   We are investigating reports of user accounts being changed to pending status for tenants integrated with Active Directory Bridge.

2. investigating 2025-05-02 12:08 UTC

   We are continuing to investigate reports of user accounts being changed to pending status for tenants integrated with Active Directory Bridge. We will share another update in one hour.

3. identified 2025-05-02 13:19 UTC

   We have identified the cause of the issue and a fix is being implemented. We will share another update in one hour.

4. identified 2025-05-02 14:26 UTC

   We have identified the cause of the issue and are refining the fix to be implemented. We will share another update in one hour.

5. identified 2025-05-02 15:24 UTC

   We have reverted the update which caused the initial impact. There should be no new occurrences. We are creating a remediation plan at this time and will share it as soon as it is ready. We will share another update in one hour.

6. identified 2025-05-02 16:34 UTC

   We are in the process of validating our remediation plan. We will communicate it as soon as it is ready. We will share another update in one hour.

7. identified 2025-05-02 17:42 UTC

   We have identified a fix for this issue. We have validated our remediation plan and are implementing it now. The plan will take several hours to complete. We will provide another update in one hour.

8. identified 2025-05-02 18:40 UTC

   We are continuing with our implementation of our remediation plan. We anticipate several more hours to complete. We will provide another update in two hours.

9. monitoring 2025-05-02 20:30 UTC

   We have completed implementation of our remediation plan and do not anticipate any further impact. We will continue to monitor for any issues.

10. resolved 2025-05-02 22:28 UTC

    This incident has been resolved.

11. postmortem 2025-05-12 14:35 UTC

     # **Incident Report** ‌ **Date**: May 12, 2025 **Date of...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: LDAP - US Region, User Console - US Region, SSO - US Region

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-04-30 13:05 UTC

   We have identified an issue that was affecting authentication and SSO and have implemented a fix. Services have recovered and we are monitoring.

2. resolved 2025-04-30 13:15 UTC

   This incident has been resolved.

3. postmortem 2025-05-06 02:25 UTC

    # Incident Report **Date**: May 5, 2025 **Date of...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Admin Console - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-30 08:08 UTC

   We are currently investigating an issue with JumpCloud Reports failing to download. We will update the status as we learn more.

2. identified 2025-04-30 08:24 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-04-30 10:57 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-04-30 12:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Active Directory Integration - US Region

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-04-19 23:42 UTC

   The Active Directory Integration Service was found encountering errors and we are investigating the issue.

2. identified 2025-04-20 00:10 UTC

   We have identified an issue affecting the Active Directory Integration Sync and Import services, including Active Directory Delegated Authentication. This issue affects users, user updates, and password changes are not syncing between JumpCloud and Active directory, as well as...

3. identified 2025-04-20 02:12 UTC

   We are currently in the process of implementing a fix for this issue.

4. resolved 2025-04-20 02:51 UTC

   This issue has been resolved and service has now returned to normal.

5. postmortem 2025-04-23 22:15 UTC

    **Date**: Apr 23, 2025 **Date of Incident:** Apr 18, 2025...

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Password Manager - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-16 21:53 UTC

   We are currently investigating an issue with the Password Manager notifications part of our platform.

2. investigating 2025-04-16 22:06 UTC

   We are currently investigating an issue involving the distribution of Password Manager enrollment emails. We are investigating the cause of the issue currently, and will update the status event once resolved.

3. identified 2025-04-17 00:05 UTC

   We believe we have identified the issue that was impacting the distribution of the Password Manager enrollment emails. We are currently working on implementing a fix.

4. resolved 2025-04-17 00:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.

Affected: Apple MDM - US Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-09 22:33 UTC

   We are currently observing elevated error rates in the management of iOS devices. This may manifest for administrators as missing MDM tabs, impaired policy functionality, and failures in executing MDM commands.

2. identified 2025-04-10 01:21 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2025-04-10 03:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on JumpCloud's status page.