Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

JumpCloud Outage History

Every past JumpCloud outage tracked by IsDown, with detection times, duration, and resolution details.

There were 297 JumpCloud outages since March 2018. The 40 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 2, 2026

April 2026: LDAP Directory Processing Delay

Detected Apr 2, 2026 1:08 PM EDT · Resolved Apr 2, 2026 1:56 PM EDT · Duration about 1 hour

JumpCloud experienced a 49-minute delay in LDAP directory synchronizations, causing user attribute and password changes to propagate slower than expected. The team increased processing capacity to accelerate synchronizations and successfully resolved the issue.

Minor March 30, 2026

March 2026: Directory Dispatch Delays

Detected Mar 30, 2026 8:32 PM EDT · Resolved Mar 31, 2026 2:25 AM EDT · Duration about 6 hours

JumpCloud experienced dispatch delays affecting core Directory services for 5.9 hours, causing administrators to encounter delays when updating associations for users, groups, policies, directories, and commands through the Console. The team identified the root cause and worked to reduce the processing backlog by implementing fixes and increasing processing capacity. The incident was fully resolved after the backlog was cleared and normal service operations were restored.

Major March 12, 2026

March 2026: Increased error rates with JumpCloud Agent backend.

Detected Mar 12, 2026 12:54 PM EDT · Resolved Mar 12, 2026 5:52 PM EDT · Duration about 5 hours

JumpCloud experienced a 5-hour major incident where the Agent backend service had delays syncing user, command, and policy information to devices. While local agent/device logins continued to work normally (except those requiring MFA beyond TOTP), customers experienced disruptions in receiving updated configurations and policies. The engineering team identified and implemented a fix, with agent traffic returning to normal levels and full service restoration achieved.