Is JazzHR down?

We are currently investigating ongoing service degradation affecting the JazzHR platform. Customers may experience intermittent 500 Internal Server Errors, slow application performance, API instability, and issues loading billing-related profile information. Our engineers have identified the problem and are working towards a resolution. We will provide a status update by 11 am ET.

We have put in place a fix and are seeing initial positive recovery, we will continue monitoring to insure this incident is fully resolved.

This incident has been resolved. Incident Duration: June 8, 2026, 3:18 PM ET – June 9, 2026, 9:30 AM ET Service recovery began ~9:30 AM ET; full resolution confirmed and posted ~10:30 AM ET after a period of monitoring.) Impact Summary: During this window, some users may have experienced errors or been unable to access parts of the application. Cause: An internal issue affected a system that supports billing and subscription information. Because this system is used across the product, the disruption led to elevated errors and degraded access throughout the application.   Mitigation: The issue has been resolved and service has returned to normal. We are putting additional safeguards in place and do not expect it to recur. A full root cause analysis will be posted within 7–10 business days. An RCA will be provided within 7-10 business days if applicable.

**Incident Summary** On June 8–9, 2026, some users experienced errors or were unable to access parts of the application for a period of approximately 18 hours. Because the affected component supports billing and subscription information used across the product, the disruption affected general application access, not only billing pages. No customer data was lost.  **Detection** The issue was identified by internal engineering teams at approximately **4:18 PM ET on June 8**, following a significant rise in application errors and reports from Customer Support. While the symptoms were detected within an hour of the initial impact, the underlying cause required extensive investigation as it involved a silent failure of an internal component.  **Root Cause** An internal issue caused the application to lose access to cached billing and subscription data, which led it to generate an unusually high volume of requests to a third-party service we rely on. That volume exceeded the service's allowed limits, and requests were temporarily blocked, producing widespread errors.  **Resolution** Our engineering team corrected the underlying issue, significantly reduced the volume of requests to the third-party service, and restored normal operation. Service recovered by **9:30 AM ET on June 9**, and we verified the application was operating normally.  **Preventative Measures** To prevent recurrence, we are implementing the following improvements: * Preventing the internal cache from disabling itself on transient errors, and alerting immediately if it does * Reusing authenticated sessions and applying limits earlier in the request path to avoid generating excessive third-party traffic * Maintaining safe headroom under third-party limits and adding monitoring so this condition is detected within minutes

Status: Resolved Start Time: 2:30 PM EDT Duration: 10 minutes Description: We experienced a brief service interruption beginning at ~2:30 PM EDT, which may have caused intermittent access issues for some users. Impact: Users may have encountered difficulty accessing the service or experienced degraded performance during this period. Resolution: The issue was identified and resolved within approximately 10 minutes. Service has been fully restored, and systems are operating normally. Next Steps: We are reviewing the incident to prevent future occurrences.

We are aware of an issue affecting candidate search functionality within JazzHR. Candidates who have applied to job requisitions since April 29 are visible within the application list for their respective jobs, but do not appear when searched by name or email in the Candidates tab. Additionally, application history may not be consolidating correctly for some candidates, and workflow reporting may be impacted for recently applied candidates. Candidates who applied prior to April 29 remain searchable as expected. Workaround: Recently applied candidates can still be accessed by navigating directly to the job’s applicant list or by filtering the Candidates page by job. Next Steps Our Engineering team is actively investigating the root cause. We are still determining the full impact of this issue and will provide updates as more information becomes available.

The issue affecting candidate search functionality and workflow reporting within JazzHR has been identified. Candidates who have applied to job requisitions since April 29 are visible within the applicant list for individual jobs, but may not appear when searched by name or email in the Candidates tab. Additionally, application history may not be consolidating correctly, and workflow reporting may be incomplete for some recently applied candidates. Candidates who applied prior to April 29 remain searchable and unaffected. Workaround: Users can continue to access recently applied candidates by navigating directly to the job’s applicant list or by filtering the Candidates page by job. Our Engineering team is actively working on a resolution. We will provide additional updates as more information becomes available and remediation progresses.

We are continuing to work on the previously identified issue affecting candidate search functionality and workflow reporting within JazzHR. Our Engineering team has made progress, and we are beginning to see candidate search results being returned. However, work is still underway to fully resolve the issue and ensure consistent behavior across all affected areas, including application history consolidation and workflow reporting. Candidates who applied since April 29 may still experience intermittent issues, while candidates who applied prior to April 29 remain unaffected. Workaround: Recently applied candidates can continue to be accessed by navigating directly to the job’s applicant list or by filtering the Candidates page by job. We are still working to fully resolve the issue and will share additional updates as progress continues and more information becomes available.

Work continues on the previously identified issue affecting candidate search functionality and workflow reporting within JazzHR. Our Engineering team has made continued progress, and we are seeing additional improvements in search results being returned. While this indicates positive momentum, remediation efforts are still in progress to ensure full consistency across candidate search, application history consolidation, and workflow reporting. Candidates who applied since April 29 may still experience inconsistent behavior. Candidates who applied prior to April 29 remain unaffected. Workaround: Recently applied candidates can continue to be accessed by navigating directly to the job’s applicant list or by filtering the Candidates page by job. We will continue to monitor progress closely and provide further updates as resolution efforts advance.

Progress continues on the previously identified issue affecting candidate data visibility within JazzHR. Candidate Search, the Job List, and Custom Candidate Reports are now reconnected, and data has started syncing across these areas. Users should see continued improvements as the sync progresses, and we expect the majority of data to be fully caught up by end of day. Some Advanced Visual Reporting may still be impacted, and our team is actively working to restore full functionality there as well. During the syncing process, some data may appear delayed or incomplete. We are monitoring closely and will provide another update as syncing completes and remaining impacts are addressed.

The previously reported issue affecting candidate data visibility within JazzHR has been resolved, and we are now monitoring to ensure continued stability. Candidate Search, Job List, Custom Candidate Reports, and Advanced Visual Reporting (AVR) are now fully synchronized. AVR reports are actively reprocessing, and users should continue to see data populate and normalize as processing completes. We will continue to monitor system performance and data accuracy closely. If any additional issues are identified, we will provide further updates.

The issue affecting Candidate Search, Job List visibility, Custom Candidate Reports, and Advanced Visual Reporting (AVR) within JazzHR has been fully resolved. We will provide a Root Cause Analysis (RCA) within 7–10 business days. Thank you for your patience while we worked to restore full functionality.

We are investigating an issue affecting some users upon login. Users may experience SSO errors when logging in with ADP This appears to be an issue directly with ADP. We will provide further updates as soon as available.

We are currently investigating two related issues impacting our integration with ADP: Affected Services: JazzHR login via ADP (SSO) ADP candidate export to JazzHR Single Sign-On (SSO) Errors: Some users are experiencing errors when attempting to log in to JazzHR using ADP SSO. Candidate Export Issues: Candidate exports from ADP to JazzHR may be delayed or failing. At this time, we have reached out to ADP for additional details. We are unable to confirm an outage or incident on ADP’s side and are awaiting further information. Workaround Login Issues: As a temporary workaround, SSO can be disabled to allow users to log in directly to JazzHR using standard credentials. Please contact support for assistance. Export Issues: No native workaround available, please attempt to manually upload new hires to ADP and reach out to their support team if necessary. Next Steps Our team is actively monitoring the situation and has reached out to ADP to identify the root cause. We will provide updates as more information becomes available. Next Update: As soon as new details are confirmed.

Summary The issue affecting JazzHR logins via ADP Single Sign-On (SSO) and ADP candidate exports has been identified. Our team is actively working on a resolution. Affected Services JazzHR login via ADP (SSO) ADP candidate export to JazzHR Workaround SSO Login Issues: As a temporary workaround, SSO can be disabled to allow users to log in directly to JazzHR using their standard credentials. Next Steps We are actively implementing a fix and will provide additional updates as progress continues or once the issue has been fully resolved.

A fix has been successfully applied for the issue affecting JazzHR logins via ADP Single Sign-On (SSO) and ADP candidate exports. The issue originated within the integration flow and has now been addressed. Affected Services JazzHR login via ADP (SSO) ADP candidate export to JazzHR Current Status We are actively monitoring the platform to ensure continued stability and to confirm that all services are operating as expected. Next Steps Our team will continue monitoring and will share a Root Cause Analysis (RCA) within 7–10 business days.

Resolved The issue affecting JazzHR logins via ADP Single Sign-On (SSO) and ADP candidate exports has been fully resolved. A fix was applied, and services are now operating normally. Affected Services JazzHR login via ADP (SSO) ADP candidate export to JazzHR Current Status We have completed post‑deployment monitoring and confirmed system stability. No further impact is expected. Follow‑Up A Root Cause Analysis (RCA) will be shared within 7–10 business days.

We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again. ## Customer Impact From the evening of April 28 through the early evening of April 29 \(UTC\), customers using **ADP Single Sign-On \(SSO\)** were unable to log in to JazzHR via ADP. Login attempts failed during the OAuth callback step, preventing access through ADP authentication. In addition to SSO login failures, a smaller set of customers experienced issues with **ADP integration features** \(such as onboarding data pulls and candidate exports\) and a limited number of other third‑party integrations that rely on outbound connections. To minimize disruption, Customer Support temporarily disabled ADP SSO for affected tenants upon request, allowing end users to sign in using direct \(non‑SSO\) credentials until the issue was resolved. ## Root Cause A configuration change introduced as part of a routine infrastructure update caused the application to unintentionally route outbound traffic through an internal network proxy. Although the errors surfaced most visibly in ADP SSO login flows, the same underlying issue affected multiple outbound integrations during the same window. ## Resolution Once identified, the offending configuration change was fully reverted, restoring the previous behavior where outbound requests bypass the internal proxy unless explicitly required. After the corrected environment was redeployed: * Outbound connections immediately returned to normal behavior. * ADP SSO login success rates returned to baseline. * Impacted integrations recovered without requiring changes on the customer side. Customer Support then re‑enabled ADP SSO for affected tenants and confirmed restored functionality. ## Preventative Actions To reduce the likelihood and impact of similar issues in the future, we are implementing the following measures: 1. Improved Detection 2. Stronger Change Safeguards 3. Proxy Compatibility Checks 4. Faster Rollback Capabilities

Issue: Jazz ATS experienced intermittent availability and downtime. Impact: Users may have been unable to access the platform or encountered errors during the affected window. Duration: Approximately 40 minutes — from ~11:55 to ~12:35 (ET), April 20, 2026. An RCA will be provided within 7-10 business days