Last checked: 4 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: June 7, 2024, 12:07 p.m.
Description: **Date**: 2024-06-21 **Date of Incident**: 2024-06-05 **Description**: RCA for Google Apps Directory Dispatch Delay **Summary:** At approximately 20:30 MDT on 2024-06-05, JumpCloud received a large ingress of messages in a Google Apps FIFO queue. By 21:40 MDT on 2024-06-05 this exceeded 20,000 messages causing processing delays for some customers. At 21:24 on 2024-06-05 an alert fired for this delay, but was incorrectly labeled as a non-production issue, causing it to be misrouted. At 07:15 MDT on 2024-06-06 the root cause was identified and a diversion queue was constructed where those messages were moved for processing. The processing delay lasted until approximately 11:30 MDT on 2024-06-06. **Root Cause:** A contiguous block of messages larger than 50,000 from a single organization was sent to the main Google Apps FIFO queue. Normally this would initiate a diversion queue construct prior to 20,000 messages, but was missed due to an incorrect alerting change during work in the Google Apps application layer. This FIFO queue is partitioned by organization ID, and once the limit of 20,000 messages is reached, only one message at a time can be processed regardless of the number of available worker threads. #### **Contributing Factors** * **Monitoring Gaps**: Lack of effective monitoring and alerting for this queue and processing latency. * **Scaling Issues**: Workers were scaled vertically but not timely enough to handle the sudden spike in queue size. * **Delay Building Diversion Queue**: Unforeseen issues requiring manual changes extending the time to completion for the diversion queue. #### **Immediate Actions Taken** 1. **Scaling Up**: Increased the number of worker instances to process the backlog of messages. 2. **Configuration Adjustments**: Reviewed and adjusted the FIFO queue and worker settings for optimal performance. 3. **Diversion Queue**: Diversion queue created for influx of messages. #### **Long-term Corrective Actions** 1. **Automate Message Diversion**: Review and optimize diversion queue policies ensuring rapid queue build. 2. **Monitoring and Alerts**: Review and increase comprehensive monitoring and alerting mechanisms for early detection of queue build-ups and processing delays. 3. **Documentation and Training**: Document the incident and update operational runbooks.
Status: Postmortem
Impact: Minor | Started At: June 6, 2024, 11:47 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 4, 2024, 5:15 p.m.
Description: This issue has been resolved and our Premium Chat Support is fully functional at this time.
Status: Resolved
Impact: Minor | Started At: May 29, 2024, 3:46 p.m.
Description: This issue has been fully resolved. We do not expect any additional interrupts in service.
Status: Resolved
Impact: Major | Started At: May 7, 2024, 3:18 p.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.