Is Jobvite down?

We are investigating an issue affecting Email/Notification Delivery. Users may experience delayed or missing email notifications when sending interview calendar invites, evaluation forms, offer notifications, and requisition approval emails. Start time: June 2025 (intermittent) Next update: 3:00 PM PT or sooner.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results. The issue was traced to a reduction in outbound mail processing capacity caused by an infrastructure scaling issue. Mail processing hosts have been restored. We will continue to monitor email delivery performance to ensure stability. Next update: 4:30 PM PT or sooner if the issue recurs.

This incident has been resolved. Incident Duration: June 8, 2026 (intermittent) – June 11, 2026 2:30 PM PT (fully resolved) Impact Summary: Outbound email notifications — including interview calendar invites, evaluation form emails, offer letter notifications, and requisition approval emails — were intermittently delayed or not delivered, affecting multiple customer organizations. Cause: An infrastructure scaling issue reduced outbound email processing capacity, resulting in a backlog of undelivered messages. Mitigation: Our team restored email processing capacity to normal levels and reprocessed all queued messages. Email delivery is now operating normally. An RCA will be provided within 7–10 business days if applicable.

We are currently investigating an issue affecting Analytics reporting. Some users may experience reports displaying outdated data. • Start Time: 10:41 a.m. • Next Update: By 12:41 p.m. or sooner Our teams are actively working to identify the root cause and restore accurate reporting. We will provide updates as more information becomes available.

We are continuing to investigate this issue

Our teams have implemented mitigation steps and confirmed that reporting data is now updating as expected. We will continue monitoring system performance to ensure stability.

Resolved: The issue impacting Jobvite report exports has been resolved. Customer Impact: Customers reported experiencing outdated or inconsistent data, with no updated information appearing after June 3. An RCA will be provided within 7-10 business days

**Incident Summary** Between approximately June 3 and June 9, 2026, analytics dashboards did not reflect recent changes made in the ATS \(for example, candidate status updates\). All underlying data remained intact and accurate in the system of record — dashboards were delayed, not incorrect — and no data was lost.  **Detection** The issue was identified on **June 8, 2026, at 10:14 AM EDT**, following customer reports that analytics data was not updating. Although internal monitoring systems exist, they were hosted on the same server that failed, which prevented alerts from firing when the server went offline.  **Root Cause** The server responsible for syncing ATS data into the analytics platform was automatically replaced following routine infrastructure health events. Configuration issues prevented the replacement server from running the data sync process correctly, and existing monitoring did not detect the gap because it runs on the same server it monitors.  **Resolution** Once identified, our engineering team restored the server's sync capability, deployed the correct version of the sync software, and re-ran the data sync. Analytics dashboards were fully up to date by the morning of June 9. No action is required from customers, and no data was lost.  **Preventative Measures** To prevent recurrence, we are implementing the following improvements: * Fixing the server configuration so that a replaced server is fully functional automatically, without manual steps * Fixing the code deployment process so that the current version of the sync software is always deployed on a replaced server * Moving sync health monitoring to an independent system so that alerts fire even if the ETL server itself is unavailable * Formally documenting and agreeing on a complete recovery checklist across the data engineering team

Some newly posted job requisitions are not appearing on some external career websites. While positions are being created successfully, they may not consistently publish to certain branded external sites. Aggregated or combined career sites continue to display jobs as expected. Customer Impact: Candidates may be unable to view recently posted job opportunities on affected external career sites. At this time, there is no reliable workaround to force affected postings to appear. What We Know: Job data and listings are being generated correctly within the system. Some external career sites are not displaying the most recent postings. Next Steps We are actively investigating. Additional updates will be provided as more information becomes available and progress is made toward resolution

Current Status: Still Investigating Some newly posted job requisitions are not appearing on certain external career websites. While positions are being created successfully, they may not consistently publish to specific branded external sites. Customer Impact: Candidates may be unable to view recently posted job opportunities on affected external career sites. At this time, there is no reliable workaround to force affected postings to appear. What We Know: Job data and listings are being generated correctly within the system. Some external career sites are not displaying the most recent postings. Next Steps: We are still actively investigating the issue and working to identify the root cause. We will provide the next status update within 2 hours or sooner if additional information becomes available.

Current Status: Issue Identified Some newly posted job requisitions are not appearing on certain external career websites. While positions are being created successfully, they may not consistently publish to specific branded external sites. Customer Impact: Candidates may be unable to view recently posted job opportunities on affected external career sites. At this time, there is no reliable workaround to force affected postings to appear. What We Know: Job data and listings are being generated correctly within the system. The issue has been identified as the cause of delays or failures in publishing to some external career sites. Internal teams are working to address the identified cause. Next Steps: We are actively working on a fix based on the identified issue and progressing toward resolution. We will provide the next update within 2 hours or sooner as more information becomes available.

Status Update: The engineering team continues to make forward progress toward implementing a fix for this issue. We will provide the next update no later than 2 hours from now (8 pm EDT), or sooner as additional information becomes available.

Current Status: Issue Identified – Fix in Validation A fix has been applied, and the engineering team is actively validating the solution. Following a successful validation, a reindex will be performed to ensure all external career sites reflect the latest updates. We will provide the next update no later than 2 hours from now (10 pm EDT), or sooner as additional information becomes available.

Status Update: The fix has been validated, and this issue has been resolved. We have moved to a monitoring phase. Reindex tasks are currently running and may take some time to complete. This incident will remain under monitoring until we have confirmed that all reindexing has completed successfully. A Root Cause Analysis (RCA) will be made available within 7–10 business days.

Status - Resolved This issue has been fully resolved, and reindexing activities have been completed successfully. We have confirmed that all affected services are operating normally, and no further customer impact is expected. As a result, this incident is now considered closed. We appreciate your patience while we worked to restore service. A Root Cause Analysis (RCA) detailing the cause of the incident, corrective actions taken, and any preventative measures will be made available 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 Between May 27 and May 29, 2026, a subset of open job postings did not appear in search results on affected career sites. While all postings remained live within our system and no jobs or applications were lost, reduced visibility in search may have led to fewer candidate applications during this period. ## Root Cause The issue was caused by an internal search indexing component that became temporarily unavailable following routine infrastructure scaling. As a result, updates to certain job postings were not written to the search index, preventing them from appearing in search results. ## Resolution Once identified, our engineering team restored the affected indexing component and re-processed all impacted job postings. This fully restored search result accuracy. No action was required from customers at any point. ## Preventative Actions To prevent recurrence, we are implementing the following improvements: * Enhancing monitoring to directly surface indexing write failures in real time * Adding automated job-count reconciliation alerts to quickly detect discrepancies * Enabling automatic recovery for the search indexing component * Strengthening and hardening the re-indexing process for faster remediation

We have identified an issue in Production where analytics data has been delayed and has not been updated since May 21st. As a result, dashboards and reports may be displaying outdated information. Our team is actively working on a fix and will provide further updates soon.

The issue causing delayed analytics data in Production has been resolved. Data syncing has resumed; however, it may take approximately 2–3 hours for all records to fully update and reflect the latest information. We will continue to monitor to ensure full recovery.

The issue impacting analytics data delays in Production has been resolved. Data syncing is currently in progress; however, it may still take additional time for all records to update and reflect the latest information fully. We are closing this incident, but please allow time for the synchronization process to complete. An RCA will be available within 7-10 business days

**Incident Summary** Between May 21 and May 26, 2026, analytics dashboards did not reflect recent changes made in the Jobvite ATS — for example, candidate status updates appeared outdated. All underlying data remained intact and accurate in the system of record throughout this period. Dashboards were delayed, not incorrect, and no data was lost.  **Detection** The issue was identified on May 26, 2026 after customers reported that analytics dashboards were not reflecting recent ATS activity. Upon receiving these reports, our engineering team immediately began investigating.  **Root Cause** The server responsible for syncing Jobvite ATS data to the analytics platform was automatically replaced by our cloud infrastructure provider following a routine health event on May 21. A configuration error prevented the replacement server from initializing the data sync process. Because the server remained reachable at the network level, automated health checks did not flag it as unhealthy, and the sync disruption was not detected by internal monitoring during this window.  **Resolution** Once identified, our engineering team corrected the server configuration, rebuilt the server, and re-ran the full data sync. Analytics dashboards were fully up to date the same day \(May 26\). No action was required from customers, and no data was lost.  **Preventative Measures** To prevent recurrence, we are implementing the following improvements: * **Data-freshness monitoring** — Adding alerting so that any delay in analytics updates is detected within minutes, rather than relying on network-level health checks alone. * **Server build hardening** — Strengthening the server provisioning process so that replacement servers are fully functional and verified automatically, without manual intervention. * **Recovery documentation** — Formalizing and streamlining the recovery runbook to further reduce time to resolution in the event of a future issue.

Summary: We experienced an incident affecting the API service that syncs candidate data from our CRM to downstream systems. Impact: Customers may have experienced delays in seeing updated candidate information appear in the Jobvite ATS during the incident window. Affected Service: Mukmuk API Engine Timeline: Start: April 8 at approximately 2:00 AM EDT Duration: Approximately 8 hours

**Date:** April 8, 2026 **Duration:** ~11 hours \(01:00 am ET – 12:00 pm ET\) 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 On April 8, 2026, certain background processing agents responsible for moving data between Talemetry Apply and external Applicant Tracking Systems \(ATS\) were not running as expected. As a result: * Job and application data imports/exports were delayed. * Job status updates were not reflected in near real time. * Newly submitted applications were not immediately visible in the external ATS. No data was lost. All affected jobs and applications were successfully processed once service was restored. ## Root Cause The issue occurred due to a congestion condition in the Mukmuk agent processing system: * A large number of agents were scheduled to run, exceeding the capacity of the background worker pods, which were actively handling the workload. * Several non-essential agents consumed capacity, blocking higher-priority production agents, and causing the system to enter a stalled state where critical agents could not execute. In short, the system lacked sufficient safeguards to prevent inactive or non-critical agents from interfering with production workloads during peak processing conditions. ## Resolution Once the issue was identified, the following actions were taken: 1. Non-essential development agents were disabled. 2. Background processing capacity was temporarily increased to accelerate backlog processing. 3. Queued jobs were monitored until all pending imports and exports completed successfully. By approximately 12:00 ET, all agents had caught up, job processing returned to normal, and customer-facing data reflected up-to-date timestamps confirming restoration. ## Preventative Actions To reduce the likelihood and impact of similar incidents in the future, the following improvements are underway or completed: * **Proactive Monitoring** * New alerts are being added to detect stalled or non-running agents in near real time. * Monitoring schedules are being expanded beyond limited overnight checks. * **Improved Observability** * Additional metrics will track agent execution health and backlog growth. * Engineering alerts will trigger automatically when agents fail to run as expected. * **Operational Safeguards** * Cleanup of unused or churned agents to prevent resource contention. These actions will significantly reduce detection, diagnosis, and recovery times should similar conditions arise again.