Jobvite Outage History

Started Aug 06, 2026, 01:03 PM UTC· resolved Aug 06, 2026, 04:36 PM UTC

1. investigating Aug 06, 2026, 01:03 PM UTC

   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. monitoring Aug 06, 2026, 02:02 PM UTC

   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. resolved Aug 06, 2026, 04:36 PM UTC

   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. postmortem Aug 24, 2026, 07:04 PM UTC

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

Read the full incident report →

Started Jul 22, 2026, 08:46 PM UTC· resolved Jul 27, 2026, 12:22 PM UTC

1. investigating Jul 22, 2026, 08:46 PM UTC

   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.

2. investigating Jul 23, 2026, 01:19 PM UTC

   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.

3. investigating Jul 23, 2026, 10:37 PM UTC

   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.

4. monitoring Jul 23, 2026, 10:51 PM UTC

   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.

5. resolved Jul 27, 2026, 12:22 PM UTC

   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.

6. postmortem Jul 28, 2026, 12:46 PM UTC

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

Read the full incident report →

Started Jul 02, 2026, 03:22 PM UTC· resolved Jul 02, 2026, 07:07 PM UTC

1. investigating Jul 02, 2026, 03:22 PM UTC

   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.

2. investigating Jul 02, 2026, 04:32 PM UTC

   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

3. monitoring Jul 02, 2026, 04:46 PM UTC

   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.

4. resolved Jul 02, 2026, 07:07 PM UTC

   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.

5. postmortem Jul 14, 2026, 01:27 PM UTC

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

Read the full incident report →

Started Jun 22, 2026, 02:42 PM UTC· resolved Jun 22, 2026, 08:51 PM UTC

1. investigating Jun 22, 2026, 02:42 PM UTC

   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/

2. identified Jun 22, 2026, 04:17 PM UTC

   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.

3. monitoring Jun 22, 2026, 06:20 PM UTC

   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.

4. resolved Jun 22, 2026, 08:51 PM UTC

   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/

Read the full incident report →

Started Jun 18, 2026, 03:16 PM UTC· resolved Jun 18, 2026, 04:34 PM UTC

1. identified Jun 18, 2026, 03:16 PM UTC

   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.

2. resolved Jun 18, 2026, 04:34 PM UTC

   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.

Read the full incident report →

Started Jun 11, 2026, 07:56 PM UTC· resolved Jun 11, 2026, 10:25 PM UTC

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

2. investigating Jun 11, 2026, 07:56 PM UTC

   We are continuing to investigate this issue.

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

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

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

Read the full incident report →

Started Jun 08, 2026, 03:50 PM UTC· resolved Jun 09, 2026, 06:43 PM UTC

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

Read the full incident report →

Started May 29, 2026, 05:10 PM UTC· resolved Jun 01, 2026, 04:26 PM UTC

1. investigating May 29, 2026, 05:10 PM UTC

   Some newly posted job requisitions are not appearing on some external career websites. While positions are being created successfully, they may not consistently publish to certain branded external sites. Aggregated or combined career sites continue to display jobs as expected. Customer Impact: Candidates may be unable to view recently posted job opportunities on affected external career sites. At this time, there is no reliable workaround to force affected postings to appear. What We Know: Job data and listings are being generated correctly within the system. Some external career sites are not displaying the most recent postings. Next Steps We are actively investigating. Additional updates will be provided as more information becomes available and progress is made toward resolution

2. investigating May 29, 2026, 07:04 PM UTC

   Current Status: Still Investigating Some newly posted job requisitions are not appearing on certain external career websites. While positions are being created successfully, they may not consistently publish to specific branded external sites. Customer Impact: Candidates may be unable to view recently posted job opportunities on affected external career sites. At this time, there is no reliable workaround to force affected postings to appear. What We Know: Job data and listings are being generated correctly within the system. Some external career sites are not displaying the most recent postings. Next Steps: We are still actively investigating the issue and working to identify the root cause. We will provide the next status update within 2 hours or sooner if additional information becomes available.

3. identified May 29, 2026, 08:08 PM UTC

   Current Status: Issue Identified Some newly posted job requisitions are not appearing on certain external career websites. While positions are being created successfully, they may not consistently publish to specific branded external sites. Customer Impact: Candidates may be unable to view recently posted job opportunities on affected external career sites. At this time, there is no reliable workaround to force affected postings to appear. What We Know: Job data and listings are being generated correctly within the system. The issue has been identified as the cause of delays or failures in publishing to some external career sites. Internal teams are working to address the identified cause. Next Steps: We are actively working on a fix based on the identified issue and progressing toward resolution. We will provide the next update within 2 hours or sooner as more information becomes available.

4. identified May 29, 2026, 10:05 PM UTC

   Status Update: The engineering team continues to make forward progress toward implementing a fix for this issue. We will provide the next update no later than 2 hours from now (8 pm EDT), or sooner as additional information becomes available.

5. identified May 30, 2026, 12:06 AM UTC

   Current Status: Issue Identified – Fix in Validation A fix has been applied, and the engineering team is actively validating the solution. Following a successful validation, a reindex will be performed to ensure all external career sites reflect the latest updates. We will provide the next update no later than 2 hours from now (10 pm EDT), or sooner as additional information becomes available.

6. monitoring May 30, 2026, 01:10 AM UTC

   Status Update: The fix has been validated, and this issue has been resolved. We have moved to a monitoring phase. Reindex tasks are currently running and may take some time to complete. This incident will remain under monitoring until we have confirmed that all reindexing has completed successfully. A Root Cause Analysis (RCA) will be made available within 7–10 business days.

7. resolved Jun 01, 2026, 04:26 PM UTC

   Status - Resolved This issue has been fully resolved, and reindexing activities have been completed successfully. We have confirmed that all affected services are operating normally, and no further customer impact is expected. As a result, this incident is now considered closed. We appreciate your patience while we worked to restore service. A Root Cause Analysis (RCA) detailing the cause of the incident, corrective actions taken, and any preventative measures will be made available within 7–10 business days.

8. postmortem Jun 02, 2026, 04:52 PM UTC

   We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again. ## Customer Impact Between May 27 and May 29, 2026, a subset of open job postings did not appear in search results on affected career sites. While all postings remained live within our system and no jobs or applications were lost, reduced visibility in search may have led to fewer candidate applications during this period. ## Root Cause The issue was caused by an internal search indexing component that became temporarily unavailable following routine infrastructure scaling. As a result, updates to certain job postings were not written to the search index, preventing them from appearing in search results. ## Resolution Once identified, our engineering team restored the affected indexing component and re-processed all impacted job postings. This fully restored search result accuracy. No action was required from customers at any point. ## Preventative Actions To prevent recurrence, we are implementing the following improvements: * Enhancing monitoring to directly surface indexing write failures in real time * Adding automated job-count reconciliation alerts to quickly detect discrepancies * Enabling automatic recovery for the search indexing component * Strengthening and hardening the re-indexing process for faster remediation

Read the full incident report →

Started May 26, 2026, 03:47 PM UTC· resolved May 26, 2026, 08:38 PM UTC

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

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

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

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

Read the full incident report →

Started Apr 08, 2026, 06:00 AM UTC· resolved Apr 08, 2026, 05:00 PM UTC

1. resolved Apr 08, 2026, 07:57 PM UTC

   Summary: We experienced an incident affecting the API service that syncs candidate data from our CRM to downstream systems. Impact: Customers may have experienced delays in seeing updated candidate information appear in the Jobvite ATS during the incident window. Affected Service: Mukmuk API Engine Timeline: Start: April 8 at approximately 2:00 AM EDT Duration: Approximately 8 hours

2. postmortem Apr 13, 2026, 04:15 PM UTC

   **Date:** April 8, 2026 **Duration:** ~11 hours \(01:00 am ET – 12:00 pm ET\) We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again. ## Customer Impact On April 8, 2026, certain background processing agents responsible for moving data between Talemetry Apply and external Applicant Tracking Systems \(ATS\) were not running as expected. As a result: * Job and application data imports/exports were delayed. * Job status updates were not reflected in near real time. * Newly submitted applications were not immediately visible in the external ATS. No data was lost. All affected jobs and applications were successfully processed once service was restored. ## Root Cause The issue occurred due to a congestion condition in the Mukmuk agent processing system: * A large number of agents were scheduled to run, exceeding the capacity of the background worker pods, which were actively handling the workload. * Several non-essential agents consumed capacity, blocking higher-priority production agents, and causing the system to enter a stalled state where critical agents could not execute. In short, the system lacked sufficient safeguards to prevent inactive or non-critical agents from interfering with production workloads during peak processing conditions. ## Resolution Once the issue was identified, the following actions were taken: 1. Non-essential development agents were disabled. 2. Background processing capacity was temporarily increased to accelerate backlog processing. 3. Queued jobs were monitored until all pending imports and exports completed successfully. By approximately 12:00 ET, all agents had caught up, job processing returned to normal, and customer-facing data reflected up-to-date timestamps confirming restoration. ## Preventative Actions To reduce the likelihood and impact of similar incidents in the future, the following improvements are underway or completed: * **Proactive Monitoring** * New alerts are being added to detect stalled or non-running agents in near real time. * Monitoring schedules are being expanded beyond limited overnight checks. * **Improved Observability** * Additional metrics will track agent execution health and backlog growth. * Engineering alerts will trigger automatically when agents fail to run as expected. * **Operational Safeguards** * Cleanup of unused or churned agents to prevent resource contention. These actions will significantly reduce detection, diagnosis, and recovery times should similar conditions arise again.

Read the full incident report →

Started Mar 26, 2026, 08:14 PM UTC· resolved Mar 26, 2026, 11:27 PM UTC

1. investigating Mar 26, 2026, 08:14 PM UTC

   We are investigating an issue that may cause some data to be delayed in being available for reporting in Analytics starting March 22nd. No data has been lost. Further updates will be provided here as more information or a resolution is available.

2. investigating Mar 26, 2026, 08:21 PM UTC

   We are continuing to investigate this issue.

3. monitoring Mar 26, 2026, 09:10 PM UTC

   We found an issue with data transformation while moving data to the analytics layer, caused by an internal permissions issue. The internal permissions have been corrected and we can see the data updating as expected again. We will monitor this to insure it is fully addressed.

4. resolved Mar 26, 2026, 11:27 PM UTC

   This incident has been resolved, data is verified to be available in Analytics tools in the expected data sync time frame.

Read the full incident report →

Started Mar 12, 2026, 07:21 PM UTC· resolved Mar 13, 2026, 11:05 AM UTC

1. investigating Mar 12, 2026, 07:21 PM UTC

   We are investigating an issue affecting the sending of emails from the Jobvite platform. Users may experience delays in the delivery of emails triggered through the application Next update: 5 pm ET or sooner.

2. identified Mar 12, 2026, 07:33 PM UTC

   We have identified the root cause affecting Email delivery and we are working with our AWS partner to mitigate the issue. Next update: 5 pm ET or sooner

3. monitoring Mar 12, 2026, 08:25 PM UTC

   Mitigation steps have been applied, and email service functionality is returning to normal. Any new emails triggered should be sent without issue, and our teams are working to ensure the successful delivery of any emails processed during the initial incident. Next update: 7 pm ET or upon resolution.

4. monitoring Mar 12, 2026, 11:06 PM UTC

   Email service maintains stability, and new emails triggered will continue to be sent without issue Our teams are still working to ensure the successful identification and delivery of any emails processed during the initial incident. Next update: 7:30 am ET or sooner if fully resolved.

5. resolved Mar 13, 2026, 11:05 AM UTC

   This incident has been resolved. All delayed emails have been successfully reprocessed, and new emails continue to be processed successfully. An RCA will be provided within 7-10 business days.

Read the full incident report →

Started Jan 29, 2026, 09:30 AM UTC· resolved Jan 29, 2026, 10:00 AM UTC

1. resolved Jan 29, 2026, 11:38 AM UTC

   Some users experienced difficulty logging into Jobvite between 4:30 AM and 5:00 AM EST. We’ve resolved the issue, and login functionality has been fully restored.

Read the full incident report →

Started Dec 22, 2025, 01:55 PM UTC· resolved Dec 31, 2025, 02:13 PM UTC

1. identified Dec 22, 2025, 01:55 PM UTC

   We have identified an issue resulting in unexpected errors when attempting to complete certain onboarding tasks. Our engineers are actively working on a resolution

2. identified Dec 22, 2025, 05:41 PM UTC

   Update: We are continuing to have issues with our onboarding module. This may be affecting the completion of new hire onboarding forms. While our teams have identified the underlying issue, we are still reviewing options for resolution. We will continue to provide periodic updates and notify as soon as this issue is resolved.

3. identified Dec 22, 2025, 10:04 PM UTC

   Update: We are experiencing an issue impacting parts of the Jobvite onboarding experience. We want to assure you upfront that this issue is isolated, understood, and actively being addressed, and that the security of your data and documents remains intact. The disruption is related to an expired document-signing certificate used for secure onboarding documents. This certificate is separate from our standard domain certificates, and recent changes in vendor ownership and industry requirements mean an updated signing mechanism is required. Our teams are actively working on a solution, including refactoring components of the system to support the new requirements. Work is underway now, and we are assessing timelines to restore full functionality as quickly and safely as possible. Current impact: -Onboarding, Offers, and native e-signature functionality are affected -Customers using DocuSign for offers are not impacted Workaround: -Offers can continue via manual signature and upload as a temporary workaround Once service is restored, we will implement additional monitoring and controls to strengthen early detection and help prevent a recurrence. We understand how critical these workflows are to your hiring process. Maintaining the security, reliability, and integrity of our platform is our top priority, and we will continue to share updates as we make progress. Please subscribe for updates and notifications

4. identified Dec 23, 2025, 03:37 PM UTC

   Current Status: We’re still working on a fix for the issue impacting parts of the Jobvite onboarding experience. The root cause has been confirmed, and our team is actively implementing changes to meet new signing requirements. Impact: Onboarding, Offers, and native e-signature functionality remain affected Customers using DocuSign for offers are not impacted Next Update: We’ll provide another update by 4 pm EST, or sooner if progress changes. Thank you for your patience as we work to restore full functionality.

5. identified Dec 23, 2025, 09:03 PM UTC

   We are continuing to work on a fix for this issue.

6. identified Dec 23, 2025, 09:04 PM UTC

   Current Status: Our teams are actively working to implement a fix for the issue impacting parts of the Jobvite onboarding experience. Engineers are working continuously to deliver a resolution as soon as possible. Impact: Onboarding, Offers, and native e-signature functionality remain affected. Customers using DocuSign for offers are not impacted. Use Cases Impacted: Uploading an attachment to a form during its creation (as an OB Admin). Uploading an attachment to a form during step completion (as a task assignee). Completing a form step (as a task assignee). This typically involves signing the document; if no signature is required, the user certifies it. Generating a PDF of all forms with collected data (Available Documents in New Hire Overview). Next Update: We’ll provide another update by 10:00 AM EST on Dec 24, or sooner if progress changes. Thank you for your patience as we work to restore full functionality.

7. identified Dec 24, 2025, 03:04 PM UTC

   Status Update as of 12/24/25: Document Signing Service We are continuing to make steady progress on restoring document signing functionality. Our teams made meaningful advances overnight and are actively testing updates today across North America, with additional work continuing tomorrow with our teams in India to maintain momentum around the clock. Once testing is completed, we will move quickly to deploy the updated signing service to production and switch the application to use it. Based on our current progress, we expect document signing to be up and running by early next week. Throughout this work, customer data remains secure and compliant with our established privacy and security standards. We appreciate your patience and want to reassure you that this remains a top priority. We will continue to share updates as milestones are reached and confirm as soon as signing functionality is fully restored.

8. identified Dec 29, 2025, 05:44 PM UTC

   Status update as of 12/29/25: Our engineering teams continue to work around the clock to resolve this issue. We’ve made solid progress securing the new certificate and are actively developing the updated storage and retrieval process required to use it. We are pursuing both the full long‑term fix and a potential short‑term workaround in parallel. At this time, we do not expect the full solution to be ready before Wednesday, unless the short‑term option proves successful sooner. We will keep you updated as we make further progress. Thank you for your continued patience.

9. identified Dec 30, 2025, 04:27 PM UTC

   Our team has completed development of our new document‑signing service and has successfully deployed it to production. We are now preparing and deploying an additional update that will enable our Onboarding and Jobvite integrations to use this new service, with this work expected to be finalized early this afternoon. Once all components are live, we will conduct full end‑to‑end testing in our production environment to ensure everything operates as intended. We are targeting deployment of the full fix on Wednesday, provided all testing is completed successfully.

10. resolved Dec 31, 2025, 02:13 PM UTC

    All components of the new document‑signing service, including Onboarding and Jobvite integrations, have been successfully deployed to production. Full end‑to‑end testing has been completed, and everything is operating as expected. The fix is now fully live. We will continue monitoring the system closely to ensure stability and optimal performance. Thank you for your patience and understanding while we worked to resolve this issue. A Root Cause Analysis (RCA) will be provided within 5–7 business days.

11. postmortem Jan 09, 2026, 08:13 PM UTC

    **Customer Impact** On December 22, 2025, customers experienced an interruption to digital document signing capabilities within Jobvite. This impacted workflows that rely on native onboarding and native e‑signature functionality. All customers using document signing features were affected during the incident window. **Root Cause** The service disruption was caused by the expiration of a digital signing certificate required to sign documents. The certificate expired on December 22, 2025, and was not renewed prior to expiration. Several environmental and industry changes contributed to the complexity of the issue, including evolving certificate vendor support models and updated compliance requirements that now require hardware-based security \(HSM\) signing. These changes required the implementation of a new, compliant signing approach rather than a standard certificate renewal. **Resolution** The issue was resolved by introducing a new, dedicated document signing service that complies with updated security and certification requirements. Key resolution steps included: * Issuing and deploying a new compliant signing certificate. * Implementing a new signing service built on a supported operating system and security model to enable hardware‑backed certificate signing. * Integrating the new service into existing workflows to restore document signing functionality. **Preventative Actions** We have implemented, or are actively implementing, the following actions to prevent recurrence: * **Certificate & License Management** * Establish centralized monitoring and alerting for all non‑AWS certificates and licenses. * Perform a comprehensive audit of all certificates and renewal timelines. * Migrate certificate storage and handling to secure secrets management. * **Monitoring & Alerting** * Add high‑priority alerts for document signing service availability and failures. * Introduce enhanced observability and application monitoring. * **Platform & Process Improvements** * Formalize vendor ownership, renewal responsibility, and escalation paths. * Improve deployment pipelines and testing coverage for signing workflows. * **Architecture Review** * Conduct a formal review of the document signing and conversion architecture to ensure scalability, reliability, and support for large documents. * Evaluate consolidation versus separation of document conversion and signing services based on performance and operational risk. We take the reliability of our platform seriously and recognize the impact this disruption had on customer workflows. These corrective actions are designed to significantly reduce the risk of similar outages in the future and to ensure greater visibility, resiliency, and compliance going forward.

Read the full incident report →

Started Dec 15, 2025, 02:00 PM UTC· resolved Dec 15, 2025, 02:00 PM UTC

1. resolved Dec 16, 2025, 04:06 PM UTC

   We had identified an issue that has resulted in Jobvite Analytics data not refreshing starting around December 11th, 2025. Our engineers have since corrected the problem and updated all affected data.

2. postmortem Dec 16, 2025, 04:06 PM UTC

   **Impact Summary** The application table did not update since Dec 11, 2025, causing data freshness issues. This impacted downstream processes relying on updated application data. **Root Cause** The sync process failed because a sync lock on the server was not released. This was due to release compatibility issues related to an OS upgrade. **Resolution** · Reverted the problematic changes · Triggered a full sync to restore data freshness. The sync is currently in progress and expected to complete in a few hours. **Preventative Actions** 1. Environment Compatibility Checks 1. Implement validation to ensure changes dependent on OS upgrades are deployed only after the upgrade is complete in production. 2. Pre-Deployment Guardrails 1. Add automated checks in CI/CD pipelines to block deployment of incompatible changes. 3. Enhanced Monitoring & Alerts 1. Introduce alerts for sync lock status and abnormal termination of sync processes. 2. Implement data freshness monitoring to detect delays in updates proactively.

Read the full incident report →

Started Dec 02, 2025, 04:24 PM UTC· resolved Dec 03, 2025, 12:58 PM UTC

1. investigating Dec 02, 2025, 04:24 PM UTC

   We have identified an issue affecting Job Board XML updates. Updates may be missing since November 25. Our Engineers are actively investigating.

2. identified Dec 02, 2025, 05:20 PM UTC

   The issue has been identified and we are working to catch up on all processing.

3. monitoring Dec 02, 2025, 06:36 PM UTC

   This issue has been resolved and we are actively monitoring and processing any remaining backlog

4. resolved Dec 03, 2025, 12:58 PM UTC

   This incident has been resolved.

5. postmortem Dec 17, 2025, 09:49 PM UTC

   ### What Happened? Between November 25 and December 2, 2025, our Auto-Broadcast system stopped updating job board feeds and integrations. This meant that job postings were not being refreshed or sent to external job boards as expected for a period of six days. ### How Were Customers Impacted? Customers relying on timely updates to their job boards experienced delays in having their job postings refreshed or distributed. This could have affected the visibility of open positions and potentially delayed candidate applications. ### What caused the issue? * The automated process responsible for updating job board feeds stopped working because a tracking file from a previous run was not deleted as it should have been. * This leftover file caused the system to believe that updates were still in progress, so no new updates were started. * The tracking file was not deleted because the system component running the process was unexpectedly restarted before it could finish its work. * We did not have monitoring in place to alert us when this process failed. ### How was the issue resolved? * Once notified, our support and engineering teams quickly identified the cause. * The undeleted tracking file was manually removed, allowing the system to resume normal operation. * It took several hours for the system to catch up on the backlog of updates, but by the next day, all job board feeds were up to date. ### What are we doing to prevent this in the future? * We have implemented automated monitoring and alerts to notify our team immediately if the Auto-Broadcast process stops working. * We have documented troubleshooting steps to ensure a faster response if a similar issue occurs. * We are reviewing and improving the system to prevent similar failures from happening again.

Read the full incident report →

Started Nov 18, 2025, 01:18 PM UTC· resolved Nov 18, 2025, 09:06 PM UTC

1. investigating Nov 18, 2025, 01:18 PM UTC

   Some customers may experience issues with Talemetry Apply due to some problems with Cloudflare. Our engineers are actively investigating

2. identified Nov 18, 2025, 01:29 PM UTC

   Due to a global issue with Cloudflare, users may experience intermittent problems launching Talemetry Apply. Our engineers are actively working on a solution.

3. monitoring Nov 18, 2025, 02:19 PM UTC

   While the Cloudflare issues persist, our teams have mitigated the impact on our operations. We are actively monitoring for any continued problems.

4. resolved Nov 18, 2025, 09:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 01:15 PM UTC· resolved Oct 21, 2025, 12:08 PM UTC

1. identified Oct 20, 2025, 01:15 PM UTC

   We are experiencing an outage due to issues with our public cloud provider. Users may expereince intermittent preformance issues within our applications. We will provide updates as soon as they become available.

2. identified Oct 20, 2025, 03:44 PM UTC

   Due to the widespread issues with AWS affecting the US-EAST-1 Region, our Jobvite platform is experiencing some instability, resulting in intermittent availability. We will provide updates as soon as they become available.

3. identified Oct 20, 2025, 06:21 PM UTC

   Due to the widespread issues with AWS affecting the US-EAST-1 Region, our Jobvite platform continues to show instability, resulting in intermittent availability. We will provide updates as soon as they become available.

4. identified Oct 20, 2025, 08:15 PM UTC

   Our Jobvite Services are starting to show signs of recovery as AWS continues to recover from their ongoing outage. Most users are now able to login and navigate the ATS but some services and modules may still be limited. We will provide additional updates as soon as they become available.

5. identified Oct 20, 2025, 08:53 PM UTC

   Our Jobvite Services are showing signs of recovery as AWS continues to resolve their ongoing outage. Most users are now able to log in and navigate the ATS. However, we are still experiencing issues with Onboarding and resume parsing. We are actively monitoring the situation and will provide additional updates as they become available.

6. identified Oct 20, 2025, 09:12 PM UTC

   Most Jobvite Services have now been restored. however, our resume parsing vendor continues to experience residual issues. As a result, users may still encounter intermittent disruptions with our resume parsing services. We are actively monitoring the situation and will provide further updates as they become available.

7. resolved Oct 21, 2025, 12:08 PM UTC

   Early on October 20, 2025, Amazon Web Services (AWS) experienced a major outage in its US-EAST-1 (Northern Virginia) region, resulting in widespread disruptions across numerous platforms. Employ Services, along with several of our third-party vendors, were impacted by this outage, leading to intermittent functionality issues and periods of inaccessibility across our systems. The issue has since been resolved, and our teams continue to actively monitor for any residual effects to ensure full platform stability.

Read the full incident report →

Started Oct 09, 2025, 02:02 PM UTC· resolved Oct 09, 2025, 05:52 PM UTC

1. investigating Oct 09, 2025, 02:02 PM UTC

   Jobvite is currenlty experiencing an outage and users may receive 503 errors., Our engineers are actively investigating

2. identified Oct 09, 2025, 02:52 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Oct 09, 2025, 03:06 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Oct 09, 2025, 05:52 PM UTC

   This incident has been resolved.

5. postmortem Oct 24, 2025, 06:06 PM UTC

   **Incident Date:** October 9, 2025` ` **Start Time:** 9:20 AM ET` ` **End Time:** 10:17 AM ET \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Impact Summary** Between 9:20 AM and 10:20 AM ET on October 9, 2025, users experienced 503 errors within the Jobvite application, making it temporarily unavailable \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Root Cause** While the system components were healthy, they weren’t receiving traffic. The root cause was identified as a **capacity limit** on our load balancer, which prevented new application instances from registering correctly. \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Resolution** The team pinpointed a missing configuration in several services that caused all nodes to be added to the load balancer, exceeding its registration limit. We updated the configuration and manually synced the affected services. By 10:17 AM ET, services were restored and traffic resumed. Registration limits were also increased to ensure future scalability \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Preventive Actions** To avoid similar issues in the future, we’re implementing the following: * Automated alerts for service capacity limits. * A runbook for faster log analysis and troubleshooting. * Enhanced monitoring alerts to detect traffic drops in production environments.

Read the full incident report →

Started Sep 22, 2025, 06:43 PM UTC· resolved Sep 23, 2025, 12:21 AM UTC

1. investigating Sep 22, 2025, 06:43 PM UTC

   We are experiencing some intermittent issues affecting the performance and loading of the Jobvite Onboarding module. Our engineers are actively investigating the problem.

2. monitoring Sep 22, 2025, 07:31 PM UTC

   The intermittent issues are now resolved. We are actively monitoring to ensure continued stability.

3. resolved Sep 23, 2025, 12:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 31, 2025, 03:50 PM UTC· resolved Aug 01, 2025, 11:04 AM UTC

1. investigating Jul 31, 2025, 03:50 PM UTC

   We have identified an issue in Analytics affecting the loading of data in some reports. Our team is actively investigating the issue.

2. identified Jul 31, 2025, 05:24 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jul 31, 2025, 08:40 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Aug 01, 2025, 11:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 17, 2025, 04:22 PM UTC· resolved Jul 17, 2025, 08:21 PM UTC

1. identified Jul 17, 2025, 04:22 PM UTC

   We are experiencing an issue affecting the loading of data within our analytics platform. Our engineers have identified the issue and are implementing a fix.

2. identified Jul 17, 2025, 04:23 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved Jul 17, 2025, 08:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:48 PM UTC· resolved Jun 13, 2025, 10:51 AM UTC

1. identified Jun 12, 2025, 06:48 PM UTC

   An issue has been identified where there appears to be an outage with Google Cloud Services, Pillar is impacted. https://status.cloud.google.com

2. identified Jun 12, 2025, 07:56 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved Jun 13, 2025, 10:51 AM UTC

   This incident has been resolved.

4. postmortem Jun 19, 2025, 01:47 PM UTC

   On June 12, 2025, between 10:51 AM and 1:36 PM PT, Pillar experienced a service outage due to a widespread disruption within Google Cloud Platform \(GCP\), our cloud infrastructure provider. During this time, customers were unable to access the Pillar web application \([app.pillar.hr](http://app.pillar.hr)\), and Pillar integrations within Jobvite and Lever were also unavailable. The issue was caused by a global outage affecting GCP services, which directly impacted the infrastructure Pillar relies on to remain accessible. While our team closely monitored the situation, resolution was dependent on GCP restoring its services. Once the platform-wide issue was resolved, Pillar services recovered automatically. Our team also proactively reviewed the impacted period and worked to recover and restore any affected interviews where possible. However, due to the nature of the outage, we were unable to capture data from some interviews that were scheduled during the downtime. To improve our response to future incidents, we are integrating Pillar monitoring and alerting into Employ’s centralized Incident Response system and evaluating additional strategies to improve platform resilience. Moving forward, customers can view live system availability and updates anytime at [https://status.pillar.hr/](https://status.pillar.hr/). We sincerely apologize for the disruption and appreciate your continued trust in us. If you have any questions, please don’t hesitate to reach out.

Read the full incident report →

Started Jun 09, 2025, 06:56 PM UTC· resolved Jun 09, 2025, 08:57 PM UTC

1. investigating Jun 09, 2025, 06:56 PM UTC

   We are aware of an issue affecting the availability of Intelligent Messaging. Our Engineers are actively investigating the issue.

2. identified Jun 09, 2025, 07:14 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jun 09, 2025, 08:36 PM UTC

   A fix has been implemented as of 4:20 EDT and we are monitoring the results

4. resolved Jun 09, 2025, 08:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 03, 2025, 08:03 PM UTC· resolved Jun 03, 2025, 08:26 PM UTC

1. identified Jun 03, 2025, 08:03 PM UTC

   We are currently experiencing intermittent performance degradation within our Jobvite systems. Our Engineers have identified the problem and are actively working to resolve it

2. monitoring Jun 03, 2025, 08:14 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jun 03, 2025, 08:26 PM UTC

   This incident has been resolved.

Read the full incident report →