Major incident

Jobvite Operational: Jobvite Access Issues

Affected: User / Employee

Current status of Jobvite Operational: Operational — live Jobvite Operational status

Timeline

1. Aug 6, 2026, 13:03 UTC
   investigating
   We are currently investigating reports of issues affecting access to Jobvite. Some users are experiencing an inability to log in, while others may see errors (including Bad Gateway or 404) when attempting to navigate within the platform. Our engineering team is actively working on a fix. We will provide updates as more information becomes available.
2. Aug 6, 2026, 14:02 UTC
   monitoring
   A fix has been applied and service has been restored. Users should now be able to log in and navigate Jobvite normally without encountering the previously reported errors. Our engineering team is monitoring the platform to ensure stability and will provide further updates as needed.
3. Aug 6, 2026, 16:36 UTC
   resolved
   Resolved - The issues impacting access to Jobvite have been resolved. Users should now be able to log in and navigate the platform normally without encountering the previously reported errors. Our team will continue to monitor the environment to ensure ongoing stability. A Root Cause Analysis (RCA) will be made available within 7-10 business days.
4. Aug 24, 2026, 19:04 UTC
   postmortem
   **Incident Summary** between approximately 8:06 AM and 9:04 AM EDT, some users may have experienced difficulty logging in or intermittent unavailability while our team completed a routine production deployment. **Detection** The issue was identified internally during deployment verification and escalated immediately to internal teams. **Root Cause** A server instance involved in the deployment was unexpectedly replaced by our cloud provider. While a replacement was provisioned automatically, restoring it to active service required a manual step, extending the disruption. **Resolution** Engineering manually restored the replacement server to active service, returning the system to normal operation by 9:04 AM EDT. **Preventative Measures** * **Automation:** Automating the step that currently requires manual intervention to restore a replaced server to service. * **Monitoring:** Adding alerting for server replacement events and for disk/CPU saturation on affected servers, and reconciling deployment-pipeline status against actual deployment outcome so failures cannot go undetected. * **Housekeeping:** Implementing log rotation on affected servers to prevent disk space exhaustion.

Updates as published by Jobvite Operational (original).