Jobvite experienced a minor incident on May 26, 2026 affecting Reporting, lasting 4h 50m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 26, 2026, 03:47 PM UTC
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.
- monitoring May 26, 2026, 06:25 PM UTC
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.
- resolved May 26, 2026, 08:38 PM UTC
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
- postmortem Jun 05, 2026, 07:21 PM UTC
**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.