JazzHR Outage History

Started Oct 21, 2026, 07:09 PM UTC· resolved Oct 21, 2026, 10:22 PM UTC

1. investigating Oct 21, 2026, 07:09 PM UTC

   We are investigating an issue affecting Career Page settings in JazzHR. Users may see an "Access Denied" error when clicking Save Changes on the Career Page Layout settings page (Settings > Jobs). Changes made on this page are not saved. Public career pages and candidate applications are not affected at this time.

2. identified Oct 21, 2026, 07:12 PM UTC

   We’ve identified the Cloudflare rule blocking saves on the Career Page Layout page. SRE is investigating why this route triggers a false positive. We’ll update the team as soon as we know more.

3. monitoring Oct 21, 2026, 08:01 PM UTC

   A fix has been implemented, and we have confirmed that changes to the Career Page layout can now be saved successfully. We will continue to monitor the results.

4. resolved Oct 21, 2026, 10:22 PM UTC

   Resolved – JazzHR – Unable to Save Career Page Settings Incident Duration: Oct 21, 2026, ~11:25 AM – 12:40 PM (status page posted 12:15 PM; fix confirmed working 12:52 PM) Impact Summary: Some customers couldn't save changes on the Career Page Layout page (Settings > Jobs). The block page appeared when they tried to save. Other parts of JazzHR weren't affected. Cause: A Cloudflare security rule that protects against a known vulnerability wrongly flagged the save request on that page. The rule had been re-enabled for security reasons. Mitigation: Our engineering team deployed a fix that stops the rule from blocking this page. Saving career page settings works normally again. We apologize for any inconvenience. If you still have trouble saving changes for Career Page Layouts, please reach out to JazzHR Support for further assistance.

Read the full incident report →

Started Oct 21, 2026, 03:04 PM UTC· resolved Oct 21, 2026, 05:34 PM UTC

1. identified Oct 21, 2026, 03:04 PM UTC

   JazzHR eSignature functionality is currently unavailable. Our eSignature partner, Dropbox Sign, is performing emergency maintenance that began at approximately 7:20 AM PT. They took their service offline as a precaution after identifying security vulnerabilities in a software component. They are applying patches now. Impact: Offer letters and other documents can't be sent for signature. Jobseekers and other signers can't open or sign documents, including embedded signing. Completed signed documents may not be delivered or updated in JazzHR until service is restored. Errors may appear when using any JazzHR eSignature feature. Other JazzHR functionality isn't affected. Next steps: Dropbox Sign hasn't given a restoration time yet. We're monitoring their progress and will update this page as we have more information. No action is needed from customers. After service is restored, retry any failed sends or signatures. If a document is stuck after service is restored, contact Support. We apologize for the disruption and thank you for being a JazzHR customer.

2. monitoring Oct 21, 2026, 04:27 PM UTC

   JazzHR eSignature functionality is showing as restored. Our eSignature partner, Dropbox Sign, finished its emergency maintenance and reported its systems back online at approximately 9:15 AM PT. The outage began at approximately 7:20 AM PT, so eSignature features were unavailable for about two hours. What was affected: Sending offer letters and other documents for signature. Signing documents, including embedded signing. Delivery of completed signed documents. Next steps: We're monitoring to confirm that eSignature features are working normally in JazzHR. Retry any sends or signatures that failed during the outage. If a document is still stuck, or a completed document hasn't updated, contact Support. We'll post a final update once we've confirmed everything is stable. We apologize for the disruption.

3. resolved Oct 21, 2026, 05:34 PM UTC

   JazzHR eSignature functionality has been restored and is operating normally. Thank you for your patience. Incident Duration: Oct 21, 2026, approximately 7:20 AM – 9:15 AM PT (about 2 hours) Impact Summary: During this time, JazzHR eSignature features were unavailable. Offer letters and other documents couldn't be sent for signature, and signers couldn't open or sign documents, including embedded signing. Delivery of completed signed documents may also have been delayed. Other JazzHR functionality wasn't affected. Cause: Our eSignature partner, Dropbox Sign, took its service offline for emergency maintenance after identifying security vulnerabilities in a software component. Mitigation: Dropbox Sign upgraded its systems to the latest secure version of PHP and brought its service back online. We monitored JazzHR eSignature activity after the service returned and confirmed it is working normally. What you may need to do: Retry any sends or signatures that failed during the incident. If a document is still stuck or a completed document hasn't updated, contact Support for further assistance. Thank you!

Read the full incident report →

Started Oct 16, 2026, 02:42 PM UTC· resolved Oct 16, 2026, 06:47 PM UTC

1. investigating Oct 16, 2026, 02:42 PM UTC

   We are currently investigating an issue affecting the JazzHR Basic Widget. Job listings embedded on external career sites using the Basic Widget may fail to display, resulting in a blank space where open positions normally appear. Impacted Workflows: Candidates visiting external website career pages using the embedded Basic Widget are unable to view or apply for open positions. This issue is isolated to external websites utilizing the Basic Widget. Our Engineering team has been engaged and is actively diagnosing the root cause.

2. identified Oct 16, 2026, 02:57 PM UTC

   Our Engineering team has identified the underlying cause and is actively working on a resolution. We will continue to provide updates as progress is made toward full restoration of service.

3. monitoring Oct 16, 2026, 03:36 PM UTC

   A fix has been implemented to address the issue affecting the JazzHR Basic Widget. Job listings embedded on external career sites should now be displaying as expected. Our team is actively monitoring system performance and application behavior to ensure the fix remains effective and that service stability is fully restored.

4. resolved Oct 16, 2026, 06:47 PM UTC

   Resolved The issue affecting the JazzHR Basic Widget has been fully resolved. Following the implementation of the fix and a period of enhanced monitoring, job listings embedded on external career sites are displaying and functioning as expected. Our Engineering team identified the root cause, implemented a corrective fix, and validated service restoration. Monitoring has confirmed stable performance, and no further impact has been observed. A detailed Root Cause Analysis (RCA) is currently being prepared and will be made available within 7-10 business days. We apologize for any inconvenience this issue may have caused and appreciate your patience while we worked to restore service.

5. postmortem Oct 21, 2026, 12:41 PM UTC

   **Incident summary** On October 16, 2026, job listings embedded on some external career sites through the JazzHR Basic Widget failed to display. Candidates visiting affected sites saw a blank area where open jobs normally appeared. The issue did not affect the JazzHR Advanced Widget. The impact began at approximately 09:15 UTC and service was restored at 15:19 UTC. **Detection** The issue was identified after customers contacted our Support team. Engineering reproduced the problem and found that browsers were refusing to load the Basic Widget script because its declared content type did not match the content it returned. **Root cause** A security update required browsers to enforce declared content types more strictly. The Basic Widget returned JavaScript but was incorrectly labeled as HTML by an older response-handling path. Browsers therefore blocked the script instead of displaying job listings. **Resolution** Engineering corrected the response handling so the Basic Widget is served with the proper JavaScript content type. The change was tested in staging, deployed to production, and verified on affected customer sites. Customers did not need to update or reinstall their widget code. **Preventative measures** To prevent a recurrence of this issue and improve our response to similar incidents, the following actions have been taken or are planned: · **Code Improvements**: Automated tests were added to the response-handling bridge to ensure content types are preserved and correctly declared. · **Enhanced Monitoring**: A new synthetic smoke test has been proposed to simulate a browser loading the Basic Widget. This will allow for automated detection of rendering issues before they impact customers. · **Validation Updates:** The checklist for global security changes has been updated to include representative browser-integrated workflows, ensuring cross-site scripts are exercised during pre-deployment testing.

Read the full incident report →

Started Aug 31, 2026, 05:52 PM UTC· resolved Aug 31, 2026, 10:10 PM UTC

1. investigating Aug 31, 2026, 05:52 PM UTC

   We are currently investigating an issue affecting the Indeed Apply functionality for job listings published through JazzHR. Customer Impact: Candidates applying to jobs on Indeed may not see the inline Indeed Apply option and will instead be redirected to complete their application on your company's career page. Career page applications are fully operational and unaffected. Our engineering team is actively investigating, and we will provide an update as soon as more information is available.

2. identified Aug 31, 2026, 06:22 PM UTC

   We have determined that the Indeed Apply option was not showing as applied in all cases due to an error made during a recent update that affected how data was loaded into the feed provided to Indeed. We are working on a correction and will be deploying it as soon as practical. We will provide further information here as it becomes available and when we have verified the fix is deployed.

3. monitoring Aug 31, 2026, 06:58 PM UTC

   We have deployed a fix for the data being sent to Indeed and verified that our outbound data is now fully as Indeed expects it to be. We are monitoring this to insure no further changes are needed on our side and that the changes are seen by Indeed and actioned in job postings. We apologize for the inconvenience and appreciate you being a JazzHR customer.

4. resolved Aug 31, 2026, 10:10 PM UTC

   We have verified the data feed to Indeed is now fully correct from our side and the feed has updated to reflect this. Jobs on Indeed that are not correctly showing the Indeed Apply option should be corrected during Indeed's next data ingest and processing event, which Indeed typically runs every 4 hours. We will continue to watch this area to insure no other issues arise.

5. postmortem Sep 01, 2026, 01:55 PM UTC

   **Incident Summary** Between August 26 and August 31, 2026, a technical issue affected the "Indeed Apply" feature for job postings. While job listings were still visible on Indeed, the streamlined application process was temporarily unavailable, and applicants were instead directed to complete their applications on employer career sites. **Detection** The issue was identified on August 31, 2026, at 1:48 PM EDT following reports from customers and our integration partners. A review of system logs confirmed that the impact began on August 26, 2026. Because the job listings themselves continued to post successfully, standard automated alerts did not immediately signal the specific failure of the integrated application tool. **Root Cause** The interruption was caused by a configuration issue during a routine security enhancement. This resulted in the job feed being sent without the required security token, which is necessary to validate and enable the "Indeed Apply" functionality. **Resolution** Once the issue was reported, our engineering team identified the missing configuration within minutes. The following steps were taken to restore service on August 31, 2026: * Configuration Correction: The data packaging process was updated to ensure the security token is correctly included. * System Update: A corrected version of the service was deployed at 2:38 PM EDT. * Data Refresh: The job feed was fully regenerated and validated by 2:51 PM EDT. * Verification: Our team performed a manual audit of the updated feed at 2:55 PM EDT to confirm that all security credentials were functioning as expected. **Preventative Measures** We are committed to maintaining a seamless experience for recruiters and candidates. To prevent this from happening again, we are implementing the following: * Enhanced Automated Testing: We have added new validation steps that specifically check for the presence of required application metadata before any job feed is published. * Process Audit: We have conducted a full review of our configuration management to ensure all service pathways are included in future security updates. * Improved Monitoring: We are developing more granular monitoring tools to alert our teams specifically if partner-integrated features become unavailable, even if general job posting remains active. * Updated Procedures: We have refined our internal deployment guides to ensure all necessary dependencies are verified during the update process.

Read the full incident report →

Started Aug 24, 2026, 02:10 PM UTC· resolved Aug 24, 2026, 03:10 PM UTC

1. investigating Aug 24, 2026, 02:10 PM UTC

   We're aware of an issue affecting the Office 365 Calendar integration, which began around 9:00 PM ET on August 23, 2026. Customers using this integration may experience errors when connecting or syncing calendar data. Workaround: • Coordinate directly via external email/calendar clients: Schedule interviews and verify free/busy availability natively within Outlook or Office 365. • Reporting & tracking impact: Note that interviews scheduled directly in external clients will not automatically sync to JazzHR, which will temporarily affect interview tracking and reporting functionality until service is restored. Our teams are actively working on a fix

2. resolved Aug 24, 2026, 03:10 PM UTC

   Resolved: The issue affecting the Office 365 Calendar integration, which began around 9:00 PM ET on August 23, 2026, has been resolved. Customers should now be able to connect and sync calendar data normally. Our team has confirmed that service has been fully restored and is continuing to monitor the integration to ensure stability. Any new interviews or calendar updates should now sync as expected. We appreciate your patience while we worked to resolve this issue and apologize for any inconvenience caused. An RCA will be available within 7-10 business days

Read the full incident report →

Started Aug 10, 2026, 06:00 PM UTC· resolved Aug 10, 2026, 06:06 PM UTC

1. resolved Aug 10, 2026, 07:52 PM UTC

   Window: 14:01:44.592 - 14:08:02.363 EDT (6 min 18 s) Impact: JazzHR application was completely unavailable. Cause: Upgraded PHP 8.2 runtime rejecting type coercions PHP 7.4 runtime allowed Status: Resolved. Prod back on PHP 7.4 with previous stable release 6.74.0 We had a brief, approximately 6 minute, window of time where the JazzHR. platform was unavailable as a result of errors that occurred after an update deployment. The platform was unavailable for use for 6 min 18 s and restored afterwards by reverting the deployment. We have identified the areas causing these issues and are working on corrections as well as identifying why our pre-deployment testing did not identify these errors. Thank you for being a JazzHR customer!

Read the full incident report →

Started Jul 21, 2026, 09:02 PM UTC· resolved Jul 22, 2026, 11:37 AM UTC

1. identified Jul 21, 2026, 09:02 PM UTC

   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.

2. monitoring Jul 21, 2026, 11:20 PM UTC

   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.

3. resolved Jul 22, 2026, 11:37 AM UTC

   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.

Read the full incident report →

Started Jun 22, 2026, 02:42 PM UTC· resolved Jun 22, 2026, 06:21 PM UTC

1. investigating Jun 22, 2026, 02:42 PM UTC

   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/

2. identified Jun 22, 2026, 04:17 PM UTC

   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.

3. resolved Jun 22, 2026, 06:21 PM UTC

   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.

Read the full incident report →

Started Jun 18, 2026, 02:40 PM UTC· resolved Jun 22, 2026, 11:44 AM UTC

1. investigating Jun 18, 2026, 02:40 PM UTC

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

2. identified Jun 18, 2026, 02:46 PM UTC

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

3. monitoring Jun 18, 2026, 05:16 PM UTC

   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.

4. monitoring Jun 19, 2026, 03:22 PM UTC

   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.

5. resolved Jun 22, 2026, 11:44 AM UTC

   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

Read the full incident report →

Started Jun 09, 2026, 09:18 PM UTC· resolved Jun 15, 2026, 02:58 PM UTC

1. investigating Jun 09, 2026, 09:18 PM UTC

   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.

2. investigating Jun 10, 2026, 06:57 PM UTC

   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

3. investigating Jun 10, 2026, 09:43 PM UTC

   We are continuing to investigate this issue.

4. identified Jun 11, 2026, 06:34 PM UTC

   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.

5. monitoring Jun 12, 2026, 07:07 PM UTC

   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.

6. resolved Jun 15, 2026, 02:58 PM UTC

   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.

7. postmortem Jun 17, 2026, 06:29 PM UTC

   **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.

Read the full incident report →

Started Jun 09, 2026, 01:07 PM UTC· resolved Jun 09, 2026, 05:54 PM UTC

1. identified Jun 09, 2026, 01:07 PM UTC

   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.

2. monitoring Jun 09, 2026, 02:30 PM UTC

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

3. resolved Jun 09, 2026, 05:54 PM UTC

   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.

4. postmortem Jun 12, 2026, 01:31 PM UTC

   **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

Read the full incident report →

Started May 19, 2026, 06:30 AM UTC· resolved May 20, 2026, 06:30 PM UTC

1. resolved May 19, 2026, 06:52 PM UTC

   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.

Read the full incident report →

Started Apr 30, 2026, 05:33 PM UTC· resolved May 02, 2026, 06:44 PM UTC

1. investigating Apr 30, 2026, 05:33 PM UTC

   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.

2. identified Apr 30, 2026, 06:47 PM UTC

   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.

3. identified Apr 30, 2026, 11:53 PM UTC

   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.

4. identified May 01, 2026, 12:47 PM UTC

   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.

5. identified May 01, 2026, 05:38 PM UTC

   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.

6. monitoring May 01, 2026, 08:27 PM UTC

   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.

7. resolved May 02, 2026, 06:44 PM UTC

   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.

Read the full incident report →

Started Apr 29, 2026, 01:53 PM UTC· resolved Apr 29, 2026, 08:51 PM UTC

1. investigating Apr 29, 2026, 01:53 PM UTC

   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.

2. investigating Apr 29, 2026, 04:23 PM UTC

   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.

3. identified Apr 29, 2026, 06:51 PM UTC

   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.

4. monitoring Apr 29, 2026, 07:49 PM UTC

   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.

5. resolved Apr 29, 2026, 08:51 PM UTC

   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.

6. postmortem Apr 30, 2026, 04:25 PM UTC

   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

Read the full incident report →

Started Apr 20, 2026, 03:55 PM UTC· resolved Apr 20, 2026, 03:55 PM UTC

1. resolved Apr 20, 2026, 05:32 PM UTC

   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

Read the full incident report →

Started Apr 17, 2026, 03:24 PM UTC· resolved Apr 17, 2026, 08:06 PM UTC

1. monitoring Apr 17, 2026, 03:24 PM UTC

   Our WAF provider, Cloudflare is currently having DNS issues causing intermittent access to Jazz's login page. We are monitoring their progress on resolving this issue and will post an update once they have resolved it.

2. resolved Apr 17, 2026, 08:06 PM UTC

   Cloudflare has marked this incident as resolved.

Read the full incident report →

Started Apr 16, 2026, 02:12 PM UTC· resolved Apr 16, 2026, 02:28 PM UTC

1. identified Apr 16, 2026, 02:12 PM UTC

   We have identified an issue affecting email sends for Job Approval requests. Users may experience delays in receiving emails after a job is approved. Next update: 123 pm ET or sooner.

2. resolved Apr 16, 2026, 02:28 PM UTC

   This incident has been resolved. Incident Duration: 4/14;2026 @ 2:52 PM ET – 4/16/2026 @ 10:25 AM ET Impact Summary: Users experienced delays in receiving emails for Job Approval Requests

Read the full incident report →

Started Mar 28, 2026, 12:00 AM UTC· resolved Mar 28, 2026, 01:15 AM UTC

1. resolved Mar 28, 2026, 01:27 AM UTC

   We experienced a brief outage affecting access to a limited number of JazzHR sites. Incident Duration: 8:04 pm EST - 8:15 pm EST – {End} Impact Summary: Affected users may have been presented with a Cloudflare timeout error during this incident. An RCA will be provided within 7-10 business days if applicable.

Read the full incident report →

Started Mar 03, 2026, 08:02 PM UTC· resolved Mar 04, 2026, 01:41 PM UTC

1. monitoring Mar 03, 2026, 08:02 PM UTC

   We are aware that reporting data may be out of date for several users. We have identified and addressed the issue causing the delay. We are actively monitoring the data as it catches back up. Delays may continue up to 24 hours from now, but customers should have all of their current and accurate data up to February 25th.

2. resolved Mar 04, 2026, 01:41 PM UTC

   Systems have caught back up. All reporting data should now be up to date.

Read the full incident report →

Started Oct 20, 2025, 02:53 PM UTC· resolved Oct 21, 2025, 12:08 PM UTC

1. identified Oct 20, 2025, 02:53 PM UTC

   Due to the widespread AWS outage, we are experiencing intermittent issues with our resume parsing services. We will provide updates as soon as they become available.

2. identified Oct 20, 2025, 08:20 PM UTC

   Although AWS has made significant progress in their recovery efforts, our resume parsing vendor continues to experience residual issues. As a result, users may still encounter intermittent disruptions with our resume parsing services. We are actively monitoring the situation and will provide further updates as they become available.

3. resolved Oct 21, 2025, 12:08 PM UTC

   Early on October 20, 2025, Amazon Web Services (AWS) experienced a major outage in its US-EAST-1 (Northern Virginia) region, resulting in widespread disruptions across numerous platforms. Employ Services, along with several of our third-party vendors, were impacted by this outage, leading to intermittent functionality issues and periods of inaccessibility across our systems. The issue has since been resolved, and our teams continue to actively monitor for any residual effects to ensure full platform stability.

Read the full incident report →

Started Sep 24, 2025, 03:53 PM UTC· resolved Sep 25, 2025, 01:39 AM UTC

1. identified Sep 24, 2025, 03:53 PM UTC

   JazzHR is experiencing some issues and users may receive an error when accessing the application. Our Engineers are actively working on a resolution

2. monitoring Sep 24, 2025, 04:04 PM UTC

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

3. investigating Sep 24, 2025, 06:57 PM UTC

   We are again experiencing some issues resulting in slow loading pages or errors within the JazzHR application. We are actively investigating

4. monitoring Sep 24, 2025, 07:55 PM UTC

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

5. resolved Sep 25, 2025, 01:39 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 21, 2025, 02:27 PM UTC· resolved Aug 21, 2025, 02:54 PM UTC

1. monitoring Aug 21, 2025, 02:27 PM UTC

   JazzHR had experienced some performance degradation. This issue has since been resolved, and we are actively monitoring the situation.

2. resolved Aug 21, 2025, 02:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 19, 2025, 08:21 AM UTC· resolved Aug 19, 2025, 08:50 AM UTC

1. identified Aug 19, 2025, 08:21 AM UTC

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

2. monitoring Aug 19, 2025, 08:30 AM UTC

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

3. resolved Aug 19, 2025, 08:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 14, 2025, 04:27 PM UTC· resolved Aug 15, 2025, 01:59 PM UTC

1. investigating Aug 14, 2025, 04:27 PM UTC

   Our teams are actively investigating the issue

2. identified Aug 14, 2025, 05:16 PM UTC

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

3. resolved Aug 15, 2025, 01:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 12, 2025, 03:02 PM UTC· resolved Aug 12, 2025, 04:00 PM UTC

1. investigating Aug 12, 2025, 03:02 PM UTC

   JazzHR is currently experiencing a service outage. Our team is actively investigating the issue.

2. monitoring Aug 12, 2025, 03:26 PM UTC

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

3. resolved Aug 12, 2025, 04:00 PM UTC

   This incident has been resolved.

Read the full incident report →