Is Jobvite down?

We are currently investigating reports of degraded performance affecting the Jobvite ATS. Users may experience significantly slow page load times (15–45 seconds) when navigating the application, opening candidate profiles, or performing actions such as rejections and status updates. The issue appears to be intermittent. Our engineering team has been engaged and is actively investigating the root cause.  We apologize for the disruption to your recruiting workflows.

Investigating — Update Our engineering team continues to investigate the intermittent degraded performance affecting the Jobvite ATS. We do not yet have a root cause identified, and our investigation is ongoing. We appreciate your continued patience and will provide another update as our investigation progresses.

Our engineering team continues to investigate the intermittent degraded performance that has affected some Jobvite users. We do not yet have a root cause identified, and our investigation is ongoing. We appreciate your continued patience and will provide another update as our investigation progresses.

An update on this incident: service performance has returned to normal levels. Our team is actively monitoring the platform to ensure stability is maintained. We will provide a final update once we have confirmed full resolution.

The Jobvite ATS performance issue has been resolved. Our engineering team identified and addressed the cause of the intermittent latency, and system performance has returned to normal. Continued monitoring has not detected any further service degradation, and we have not received any additional customer reports since the fix was implemented. We apologize for the disruption and appreciate your patience.

**Incident Summary** Between July 20 and July 22, 2026, the Jobvite Hire platform experienced some intermittent performance degradation, primarily during business hours \(approximately 6:00 AM – 6:00 PM PT\). Some users reported slower-than-normal page loads. The issue also caused intermittent request timeouts and occasional "Host Errors" or sign-outs.  **Detection** The issue was identified through automated monitoring and internal engineering reports. On Monday, July 20, at approximately 7:27 AM PT, multiple critical alerts were triggered in our monitoring systems, indicating elevated response times, increased error percentages, and sustained garbage collection activity. Engineering teams began an active investigation at 9:40 AM PT that same morning.  **Root Cause** An internal performance-diagnostics capability, enabled in our production monitoring tooling as part of a routine investigation, consumed more application memory than expected. Under peak morning load, this reduced the resources available to serve requests, which caused the slowdowns.  **Resolution** The issue was fully resolved through the following actions: * Disabling Diagnostics: The profiling tool was disabled across the production fleet between 3:40 PM and 6:15 PM PT on July 22. Following this change, system performance immediately returned to baseline levels. * Instance Recycles: Affected application instances were recycled to clear the memory pressure. * Verification: Normal performance was verified throughout the full business day on July 23, with zero recurrence of the memory issues.  **Preventative Measures** To prevent a recurrence of this issue, we are implementing the following measures: * Restricting how and when diagnostic tooling may be enabled in production, with auditing and alerting on any such change * Adding earlier-warning monitoring so that this class of issue is detected and corrected before customers feel it * Increasing the resource headroom of the affected service

We are aware of an issue affecting user login for certain accounts. Impacted users may experience a spinning loading screen or an error when attempting to authenticate. Our team has confirmed the issue, and it is currently under active investigation. Impact: Affected users are unable to access the system. No workaround is currently available. Next Update: We will provide an update once the root cause has been identified or a fix is in progress.

Update: We have determined that this issue is intermittently affecting a limited subset of customers. Based on our current assessment, we are downgrading the impact level from an outage to a service degradation. Our engineering teams continue to actively investigate the issue and are working to identify the root cause. We will provide additional updates as more information becomes available. Impact: Affected users are unable to access the system. No workaround is currently available. Next Update: As progress is made in the investigation

Update: The issue has been resolved, and service has been restored for affected customers. Our teams have implemented corrective actions and validated the recovery of impacted services. We are continuing to closely monitor system performance and stability to ensure services remain healthy and operating as expected. Our investigation into the underlying cause remains ongoing. A detailed Root Cause Analysis (RCA), including corrective and preventive actions, will be made available within 7–10 business days. Current Status: Resolved Customer Impact: Mitigated Next Update: We will provide the RCA within 7–10 business days.

Update: The issue remains resolved, and we have not observed any new issues since service restoration. System performance and stability continue to operate within expected parameters. Our teams will continue monitoring as a precaution, but no further customer impact has been identified. Current Status: Resolved Customer Impact: None observed Next Update: A Root Cause Analysis (RCA) will be provided within 7–10 business days.

**Incident Summary** On July 2, 2026, between 08:04 PT and 09:30 PT, users may have experienced significant slowness or "hanging" when attempting to log in or save records within the application. The issue was caused by a degradation in database performance that impacted several core services.  **Detection** The issue was identified at 08:04 PT following internal reports of application unresponsiveness. Engineering teams immediately initiated an incident response bridge to diagnose the cause of the service degradation. **Root Cause** The degradation was caused by a background database query used for indexing configuration fields. This query lacked specific filters, causing it to scan and sort an excessive amount of data for certain accounts. This activity affected the database’s processing power \(CPU\), leading to a backlog that delayed other essential tasks, such as login requests and data saves.  **Resolution** To resolve the issue, Engineering transitioned operations to a fresh database instance to immediately restore processing capacity. Once the system was stable, a new database index was implemented to optimize the problematic query, allowing it to run efficiently without impacting system resources. Service returned to normal levels by 09:30 PT.  **Preventative Measures** To prevent this from occurring again, the following measures are being implemented: * **Code Optimization:** The background indexing logic is being updated to include stricter data filters, reducing the load on the database. * **Improved Monitoring:** We are adding new automated alerts to detect high database resource consumption and long-running queries before they impact users. * **Infrastructure Review:** The new database optimizations are being deployed across all environments to ensure consistent performance.

We are currently investigating an issue impacting access to our platforms. A broader Cloudflare service disruption is affecting connectivity, resulting in: Request timeouts Increased latency and slow page loads Cloudflare-generated error pages (including 5xx errors) Intermittent access to platform services Our teams are actively monitoring the situation and assessing the impact on our services. While the issue appears to originate from Cloudflare's infrastructure, we continue to monitor service health and will provide updates as additional information becomes available. Customers can monitor Cloudflare's incident status directly at: https://www.cloudflarestatus.com/ Start Time: ~9:35 EDT We apologize for the inconvenience and appreciate your patience while service providers work to restore normal operations. Customer Impact: Users may experience intermittent access issues, delayed responses, request failures, or Cloudflare error pages when accessing platform services. Reference: Cloudflare Status Page — https://www.cloudflarestatus.com/

Monitoring Third-Party Network Issue Status: We continue to monitor an ongoing third-party network incident affecting Cloudflare, which is causing intermittent timeouts, increased latency, and occasional Cloudflare error pages for some users accessing our platforms. Based on updates from Cloudflare, the issue is related to a network infrastructure event in North America, and their engineering teams are actively rerouting traffic and implementing mitigation measures to restore service stability. At this time, the underlying issue resides with a third-party provider and is outside of our direct control. Our teams are closely monitoring the situation and validating service availability as Cloudflare implements corrective actions. Customers may continue to experience intermittent connectivity issues, slow response times, or timeout errors until Cloudflare has fully resolved the incident. For the latest updates, please monitor Cloudflare's status page directly: https://www.cloudflarestatus.com/ We appreciate your patience and will continue to provide updates as new information becomes available.

Cloudflare has reported that its traffic engineering efforts have successfully mitigated the majority of congestion and packet loss associated with this incident. As a result, service conditions are improving; however, some users may still experience intermittent connectivity issues while their recovery efforts continue. Customer Impact: Most services have stabilized, but some users may continue to experience intermittent latency, timeouts, or connectivity issues during the final stages of recovery. Customers can monitor the latest updates directly on Cloudflare's status page: https://www.cloudflarestatus.com/ We will continue to provide updates as new information becomes available.

Cloudflare has reported that its traffic engineering efforts have successfully mitigated the majority of congestion and packet loss associated with this incident. Customers can monitor the latest updates directly on Cloudflare's status page: https://www.cloudflarestatus.com/

We are investigating an issue affecting our Job Alert system. Users may experience a certificate error page when trying to open links generated by the Job Alert system. We have determined that there is an issue with the certificate on our Job Alerts domain and we are working on resolving this now. Start time: 10:23AM EST Next update: 1:30PM EST or sooner.

Following our investigation, we determined that this was an isolated incident and not indicative of a widespread service disruption. The affected customer's issue has been addressed and we have observed normal service operation. No further customer impact has been identified.

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.

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