Is JazzHR down?

Issue: Some JazzHR users are experiencing an application performance issue where the platform fails to fully load, with pages remaining in a loading state indefinitely. Customer Impact: Affected users are unable to access the JazzHR platform, preventing them from managing candidates, requisitions, and other hiring workflows. No workaround is currently available. Issue Identified: Our team has identified the issue and is actively investigating.

Fix Applied — Monitoring A fix has been applied to resolve the reported issue. Our team is actively monitoring to confirm stability and ensure no recurrence. If you continue to experience any issues.

Update: The issue remains resolved, and we have not observed any new issues. System performance and stability continue to operate within expected parameters. Our teams will continue monitoring as a precaution, but no further customer impact has been identified. Current Status: Resolved Next Update: A Root Cause Analysis (RCA) will be provided within 7–10 business days.

We are currently investigating an issue impacting access to our platforms. A broader Cloudflare service disruption is affecting connectivity, resulting in: Request timeouts Increased latency and slow page loads Cloudflare-generated error pages (including 5xx errors) Intermittent access to platform services Our teams are actively monitoring the situation and assessing the impact on our services. While the issue appears to originate from Cloudflare's infrastructure, we continue to monitor service health and will provide updates as additional information becomes available. Customers can monitor Cloudflare's incident status directly at: https://www.cloudflarestatus.com/ Start Time: ~9:35 EDT We apologize for the inconvenience and appreciate your patience while service providers work to restore normal operations. Customer Impact: Users may experience intermittent access issues, delayed responses, request failures, or Cloudflare error pages when accessing platform services. Reference: Cloudflare Status Page — https://www.cloudflarestatus.com/

Monitoring Third-Party Network Issue Status: We continue to monitor an ongoing third-party network incident affecting Cloudflare, which is causing intermittent timeouts, increased latency, and occasional Cloudflare error pages for some users accessing our platforms. Based on updates from Cloudflare, the issue is related to a network infrastructure event in North America, and their engineering teams are actively rerouting traffic and implementing mitigation measures to restore service stability. At this time, the underlying issue resides with a third-party provider and is outside of our direct control. Our teams are closely monitoring the situation and validating service availability as Cloudflare implements corrective actions. Customers may continue to experience intermittent connectivity issues, slow response times, or timeout errors until Cloudflare has fully resolved the incident. For the latest updates, please monitor Cloudflare's status page directly: https://www.cloudflarestatus.com/ We appreciate your patience and will continue to provide updates as new information becomes available.

Cloudflare has reported that its traffic engineering efforts have successfully mitigated the majority of congestion and packet loss associated with this incident. As a result, service conditions are improving; however, some users may still experience intermittent connectivity issues while their recovery efforts continue. Customer Impact: Most services have stabilized, but some users may continue to experience intermittent latency, timeouts, or connectivity issues during the final stages of recovery. Customers can monitor the latest updates directly on Cloudflare's status page: https://www.cloudflarestatus.com/ We will continue to provide updates as new information becomes available.

We are currently investigating an issue where newly created jobs and job updates are not syncing to xml feed.

Our Engineering team has identified the problem and are working towards a resolution.

Update on job syndication, We identified the issue and have a fix in place, and feeds are currently regenerating. Since Job boards consume and process those feeds on their own cadence, no guarantees about timing. However, we expect to resolve the feed sync issues shortly.

All the jobs syndication is up to date as of 1500 EST (3pm) June 18, any delay is partner pulling and processing at this point.

Status: Resolved and monitoring complete. The backlog catch-up process has been completed. All job data is now fully synchronized, and newly created jobs and job updates are being delivered correctly through both the API and XML feeds. We have verified that data synchronization is operating normally and no further impact is expected. We will continue to monitor the system to ensure ongoing stability. If any further issues are identified, please reach out to customer support. An RCA will be available within 7-10 business days

Investigating — We have identified that some JazzHR customers are experiencing issues with jobs not posting to LinkedIn through the automated job syndication integration. Jobs submitted through the integration may not be appearing on LinkedIn as expected. Our Engineering team is actively investigating the issue in coordination with LinkedIn. We are working to confirm the full scope of jobs that are not posted as expected and reprocess any postings we can correct directly. In the meantime, it is possible to post a link to a job directly through LinkedIn as a temporary workaround.

We are continuing to investigate this issue, we have confirmed that most Job Publishing actions with LinkedIn are completing successfully and reviewing this with LinkedIn. If none of your jobs are publishing to LinkedIn at all, please first visit the Account Information Page and verify your LinkedIn Company ID is correctly set there. Help Center guide at https://help.jazzhr.com/s/article/Mapping-your-LinkedIn-Company-ID

We are continuing to investigate this issue.

We have identified the most likely cause of the ongoing issues with Jobs not successfully posting to LinkedIn and our engineering team is working with LinkedIn to correct the issues as soon as possible. Further updates will be provided by tomorrow or soon if more information becomes available.

We have implemented a correction for this issue where publishing jobs from JazzHR to LinkedIn was intermittently failing. We have reviewed the examples we had and are monitoring posting error rates, we believe all jobs will not publish as expected. We will continue to monitor over the weekend. Next update: Monday June 15.

This incident has been resolved. Incident Duration: June 5 - June 12 Impact Summary: Some jobs for some customers may fail to publish correctly to LinkedIn. Cause: LinkedIn has updated their preferred method of job data ingestion for job posting and there were some data conflicts caused by referencing the older method at the same time as the updated method. Mitigation: Validated integration code and system behavior to insure all publishing attempts go through the updated preferred method from LinkedIn at all times. An RCA will be provided within 7-10 business days if applicable.

**Incident Summary** Between June 5 and June 11, 2026, JazzHR customers experienced issues where job postings were failing to syndicate to LinkedIn. The issue also caused broader delays in syncing candidate, job, and workflow data across the JazzHR platform. **Detection** The issue was identified through multiple customer support reports starting around June 5, 2026. Internal monitoring did not initially trigger alerts because a software issue masked the underlying errors, making the system appear healthy in logs. Active engineering investigation began on June 11, 2026, at 1:29 PM EDT after reports were escalated. **Root Cause** The issue was caused by a breakdown in how our systems communicate and translate data. * **Missing Data Blueprints:** Our systems use "blueprints" to understand and process the information sent between JazzHR and LinkedIn. Due to a configuration error on June 4, a set of these older blueprints was accidentally removed. * **Processing Blockage:** When the system encountered job data that required those specific missing blueprints, it didn't know how to read the information. Instead of skipping the problematic data, the system became "stuck" trying to process the same records over and over. **Resolution** Engineering teams implemented a multi-step resolution on June 11, 2026: * **Error Exposure:** The software issue masking the error was fixed, allowing engineers to see the true cause of the failure. * **Queue Management:** We deployed a fix that isolates unreadable data into a separate queue for recovery. This prevented individual data errors from blocking the rest of the system, allowing us to clear the backlog and restore normal service for all customers. * **Service Restoration:** Once the blocked records were moved, the backlog of pending job postings began processing immediately. By 10:17 PM EDT on June 11, the system was unblocked, and by the morning of June 12, the majority of the data backlog had been cleared. **Preventative Measures** To prevent a recurrence of this issue, the following actions are being taken: * **Configuration Hardening:** We are verifying and locking the storage settings for data blueprints to ensure they are never prematurely deleted again. * **Enhanced Monitoring:** New alerts have been established to detect "data lag" and "unreadable records" immediately. This ensures that if a data flow stops, engineering is notified before customers are impacted. * **Standardized Error Handling:** The queue management safety mechanism is being expanded across all JazzHR data services to ensure that a single bad record cannot stop the entire system.

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