Jobvite experienced a major incident on June 11, 2026 affecting Email, lasting 2h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 11, 2026, 07:56 PM UTC
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.
- investigating Jun 11, 2026, 07:56 PM UTC
We are continuing to investigate this issue.
- monitoring Jun 11, 2026, 09:17 PM UTC
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.
- resolved Jun 11, 2026, 10:25 PM UTC
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.
- postmortem Jun 17, 2026, 07:55 PM UTC
**Incident Summary** Beginning approximately June 5, 2026, and escalating on June 11, 2026, Jobvite experienced a degradation in outbound email and notification delivery. The incident resulted in intermittent delays \(ranging from 30 minutes to several hours\) or total delivery failure for various system-generated communications. Affected services included: * **Interview Scheduling:** Google Calendar invites and candidate communications. * **Hiring Workflows:** Evaluation forms, requisition approvals, and workflow notifications. * **Offers:** Offer letters to candidates and CC'd offer notifications for recruiters. **Detection** The issue was identified through a sharp increase in customer support reports. The first isolated instance was noted on June 5, and widespread escalation was confirmed on June 11 at 3:52 PM ET. Internal investigations confirmed that no automated alerts had been triggered because the system was "silently" failing. **Root Cause** The issue was caused by a temporary shortage of available server capacity in the external cloud market. This triggered an automated system error that inadvertently deactivated healthy servers while trying to find new ones. As a result, our email delivery system was forced to run on a single server, which became overwhelmed by the volume. This caused outgoing messages to be diverted into a backlog rather than being sent to their intended recipients. **Resolution** Technical teams manually intervened on June 11 to restore service: * **Capacity Restoration:** Engineers manually unpaused the affected servers and stabilized the server fleet to ensure adequate processing power. * **Queue Reprocessing:** At 5:03 PM ET, teams began reprocessing the 60,000 backlogged messages. * **Recovery:** By 2:30 PM ET, all mail queues were drained, and normal delivery speeds were restored. * **Note:** Not all affected emails were ultimately delivered. Some messages were lost before they entered the mail queues and therefore could not be reprocessed. For those cases, related alerts were logged in the in-app notification bell icon. If a customer reports that an expected email was not delivered, advise them to check the in-app notification bell for the corresponding alert or notification. **Preventative Measures** To prevent a recurrence of this issue, the following actions are being implemented: * **Enhanced Monitoring:** New proactive alerts are being added to notify engineering teams immediately if the server count drops below required levels or if mail queues begin to back up. * **Infrastructure Stability:** We are adjusting our server configuration to guarantee a minimum number of "always-on" servers that cannot be paused by automated scaling logic, ensuring baseline capacity is always available. * **Automated Recovery:** We are developing automated tools to quickly reprocess backlogged messages without requiring manual intervention. * **Process Improvement:** A formal technical runbook has been created to help on-call engineers diagnose and resolve similar cloud-market availability issues more rapidly.