Jobvite incident

Issue Identified – Analytics Reporting

Resolved after 1 day 2 hours, affecting Reporting, on June 8, 2026.

postmortem Jun 12, 2026, 01:29 PM UTC

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

Started
Jun 08, 2026, 03:50 PM UTC
Resolved
Jun 09, 2026, 06:43 PM UTC
Duration
1d 2h
Detected by Pingoru
Jun 08, 2026, 03:50 PM UTC

Affected components

Reporting

Update timeline

  1. investigating Jun 08, 2026, 03:50 PM UTC

    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.

  2. investigating Jun 08, 2026, 06:26 PM UTC

    We are continuing to investigate this issue

  3. monitoring Jun 09, 2026, 03:47 PM UTC

    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.

  4. resolved Jun 09, 2026, 06:43 PM UTC

    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

  5. postmortem Jun 12, 2026, 01:29 PM UTC

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

Your product runs on more than Jobvite

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →