Yext Outage History

Started Jun 04, 2026, 08:16 PM UTC· resolved Jun 04, 2026, 08:30 PM UTC

1. investigating Jun 04, 2026, 08:16 PM UTC

   We are aware of an issue affecting the content library that is causing errors for some users. We are investigating and will provide an update shortly.

2. resolved Jun 04, 2026, 08:30 PM UTC

   We have identified and remediated the issue. We confirmed there was no impact to customers. This incident is resolved.

Read the full incident report →

Started Jun 03, 2026, 08:15 PM UTC· resolved Jun 03, 2026, 10:38 PM UTC

1. investigating Jun 03, 2026, 08:15 PM UTC

   We are investigating reports of reports asynchronously generated via the Analytics API being inaccessible. Our team is actively working to identify the root cause. We will update this page when we have further information.

2. monitoring Jun 03, 2026, 08:52 PM UTC

   We have remediated the issue, and all new reports requested via the Analytics API should now be accessible. Clients who are encountering errors with loading previously-generated reports should make a new request to the Analytics API to regenerate their desired reports. We will continue to monitor the situation.

3. resolved Jun 03, 2026, 10:38 PM UTC

   The issue affecting Analytics API has been resolved. As previously noted, all new reports requested via the Analytics API should now be accessible. Clients who are encountering errors with loading previously-generated reports should make a new request to the Analytics API to regenerate their desired reports.

Read the full incident report →

Started Jun 03, 2026, 08:52 AM UTC· resolved Jun 03, 2026, 11:03 AM UTC

1. investigating Jun 03, 2026, 08:52 AM UTC

   We are currently experiencing degraded performance affecting parts of the Reviews Portal. Some users may encounter increased latency and intermittent errors when accessing certain functionality. Our team is actively investigating and working to mitigate the issue. We will provide additional updates as more information becomes available. Impact: Reviews Portal performance may be degraded, including intermittent errors and slower response times.

2. monitoring Jun 03, 2026, 09:43 AM UTC

   We have identified and mitigated the issue that was causing degraded performance in the Reviews Portal and related functionality. System load has returned to normal levels, and service performance has stabilized. We are continuing to monitor the platform closely to ensure the recovery is sustained. Users should no longer experience the elevated latency, timeouts, or intermittent errors reported earlier.

3. resolved Jun 03, 2026, 11:03 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 02, 2026, 05:32 PM UTC· resolved Jun 03, 2026, 06:10 PM UTC

1. investigating Jun 02, 2026, 05:32 PM UTC

   We have identified an issue where a subset of Managed Services ETLs that rely on SFTP file drops failed. We are working on identifying the impacted jobs and time frame.

2. identified Jun 02, 2026, 06:09 PM UTC

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

3. resolved Jun 03, 2026, 06:10 PM UTC

   We have completed our impact assessment and are following up directly with any affected clients. We will continue to monitor closely to ensure normal processing is maintained.

4. postmortem Jun 12, 2026, 07:36 PM UTC

   # **Summary** From approximately 6:45PM ET on Sunday, June 1, 2026, until 2:06PM ET on Monday, June 2, 2026, a subset of customers using Yext Managed Services ETL workflows experienced processing failures related to a Yext-managed file ingestion service. During this period, a capacity constraint within a Yext-managed file ingestion service prevented some incoming files from being fully processed, causing downstream ETL processing failures. For a small number of customers, incomplete data resulted in incorrect business hours being published to listing publishers. Subsequent successful ETL runs restored the correct information, and verification completed on June 3 confirmed normal processing had resumed for all affected customers. # **Root Cause** The issue occurred when a capacity constraint developed within infrastructure supporting Managed Services file ingestion workflows. As available capacity was exhausted, some incoming files could not be fully written and were stored as incomplete files. These files were subsequently processed by downstream ETL workflows, resulting in processing failures and data errors issues for a subset of customers. The issue was not detected immediately because the failure condition was not surfaced by the automated checks and alerts in place at the time. Consequently, the issue was identified after customer impact had begun. We have identified this monitoring gap and are implementing additional monitoring and alerting to improve detection and response times for similar issues. # **Remediation** After identifying the issue, the team restored capacity on the affected service, returning file ingestion and processing to normal operation at 2:06PM ET on June 2. We have identified and are implementing several follow-up actions to prevent similar incidents in the future, including: * Adding additional monitoring and alerting for critical Managed Services file ingestion infrastructure. * Implementing automated capacity management and retention controls to reduce the risk of resource exhaustion. * Improving validation of incoming files so incomplete files are detected and rejected before downstream processing.

Read the full incident report →

Started May 20, 2026, 12:17 PM UTC· resolved May 20, 2026, 04:37 PM UTC

1. investigating May 20, 2026, 12:17 PM UTC

   We are currently investigating elevated error rates from LinkedIn APIs used by Hearsay Social to monitor LinkedIn user activity, including posts, comments, and profile updates. Customers may experience delays in LinkedIn activity capture and monitoring. We are working with LinkedIn and monitoring recovery. We will provide another update as more information becomes available.

2. monitoring May 20, 2026, 03:56 PM UTC

   LinkedIn has implemented a fix and we are monitoring results.

3. resolved May 20, 2026, 04:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 19, 2026, 03:07 PM UTC· resolved May 19, 2026, 04:19 PM UTC

1. investigating May 19, 2026, 03:07 PM UTC

   We are seeing degraded performance with some areas of the Hearsay application likely due to heavy traffic. We are actively investigating and will update shortly. No data loss is expected at this time

2. identified May 19, 2026, 03:59 PM UTC

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

3. monitoring May 19, 2026, 04:02 PM UTC

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

4. resolved May 19, 2026, 04:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 13, 2026, 05:24 PM UTC· resolved May 13, 2026, 08:40 PM UTC

1. monitoring May 13, 2026, 05:24 PM UTC

   We have identified errors in the Listings pages within the portal. We have remediated the errors and will continue to monitor the situation.

2. resolved May 13, 2026, 08:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 12, 2026, 10:33 PM UTC· resolved May 13, 2026, 11:45 PM UTC

1. identified May 12, 2026, 10:33 PM UTC

   We have identified an issue that has been causing delays in Crawler runs since 4:00 AM EST earlier today (May 12, 2026).

2. identified May 13, 2026, 06:37 AM UTC

   Crawler runs are still delayed; we are continuing to work on figuring out the source of the delays.

3. monitoring May 13, 2026, 06:10 PM UTC

   We have resolved the delays causing Crawler runs to be stuck over the last ~34 hours. As part of our resolution, we needed to cancel all active crawls. For customers with one-off or weekly crawl configurations, we have restarted all your crawls (and all but five weekly crawls are still in progress). For customers with daily crawl configurations, you should feel free to manually restart your crawls, or expect that they will run again at their normally scheduled time in the next 24 hours.

4. resolved May 13, 2026, 11:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 12, 2026, 04:09 PM UTC· resolved May 13, 2026, 04:34 PM UTC

1. investigating May 12, 2026, 04:09 PM UTC

   Due to some underlying infrastructure issues we are working to resolve, data updates in Yext Search may be delayed and Review Language classification is down in Yext Reviews.

2. identified May 12, 2026, 06:57 PM UTC

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

3. identified May 12, 2026, 07:05 PM UTC

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

4. monitoring May 12, 2026, 08:32 PM UTC

   A fix has been implemented and we are monitoring the impacted systems.

5. resolved May 13, 2026, 04:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 30, 2026, 09:30 PM UTC· resolved Apr 30, 2026, 09:30 PM UTC

1. resolved Apr 30, 2026, 11:39 PM UTC

   An issue with the US Customer Portal was identified and mitigated. Between 5:30pm and 6:10pm ET on 4/30/2026, the portal may have been unavailable or the navigation bar may have failed to render. The portal is now operating normally.

Read the full incident report →

Started Apr 29, 2026, 01:34 PM UTC· resolved Apr 30, 2026, 01:30 PM UTC

1. investigating Apr 29, 2026, 01:34 PM UTC

   We are currently investigating reports of publishing delays for a subset of Pages sites.

2. identified Apr 29, 2026, 02:19 PM UTC

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

3. monitoring Apr 29, 2026, 05:10 PM UTC

   We have implemented a fix for this issue and publishing has resumed. There was also a partial impact to the Content Portal which has also been mitigated. We will continue to monitor the situation.

4. resolved Apr 30, 2026, 01:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2026, 09:54 AM UTC· resolved Apr 22, 2026, 01:29 PM UTC

1. investigating Apr 22, 2026, 09:54 AM UTC

   We are investigating reports of a partial outage in Analytics API

2. identified Apr 22, 2026, 10:33 AM UTC

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

3. identified Apr 22, 2026, 11:34 AM UTC

   We have mitigated the issue for most affected customers. We are continuing to work on completely resolving the issue.

4. monitoring Apr 22, 2026, 12:17 PM UTC

   We have remediated the issue. We will continue to monitor the situation.

5. resolved Apr 22, 2026, 01:29 PM UTC

   This incident is resolved.

Read the full incident report →

Started Apr 09, 2026, 06:00 PM UTC· resolved Apr 09, 2026, 07:03 PM UTC

1. monitoring Apr 09, 2026, 06:00 PM UTC

   A issue delaying Managed Services ETLs was identified and mitigated. Between 1:15am and 12:52pm ET on 4/9/2026, Managed Services ETLs were delayed in running. All systems are now operating normally, any delayed data updates will be processed, and our teams are monitoring. We will provide a final update by 3:00pm ET on 4/9/2026.

2. resolved Apr 09, 2026, 07:03 PM UTC

   This incident is resolved.

Read the full incident report →

Started Apr 08, 2026, 10:21 AM UTC· resolved Apr 08, 2026, 01:00 PM UTC

1. investigating Apr 08, 2026, 10:21 AM UTC

   We are investigating reports of delays in processing of automated and generative review responses.

2. identified Apr 08, 2026, 10:25 AM UTC

   We have identified the issue and are working on remediation.

3. monitoring Apr 08, 2026, 11:10 AM UTC

   We have remediated the issue, and are processing the delayed data. We will continue to monitor the situation.

4. resolved Apr 08, 2026, 01:00 PM UTC

   All delayed items have been processed and are now operating in the expected timeframe for new responses. This incident is resolved.

Read the full incident report →

Started Mar 19, 2026, 03:16 PM UTC· resolved Mar 19, 2026, 10:35 PM UTC

1. identified Mar 19, 2026, 03:16 PM UTC

   We have identified an issue with detect-in for native video posts not functioning in Supervision for some users. This does not affect video posts published from within the Hearsay platform. We are working to mitigate the problem.

2. monitoring Mar 19, 2026, 06:39 PM UTC

   We have deployed a fix to detect-in for native video posts in Supervision. We will continue to monitor for any adverse effects.

3. resolved Mar 19, 2026, 10:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 18, 2026, 10:51 PM UTC· resolved Mar 19, 2026, 02:15 AM UTC

1. identified Mar 18, 2026, 10:51 PM UTC

   Due to this ongoing incident, customers may not see updates to Japanese profiles properly reflected in their Search experience.

2. monitoring Mar 18, 2026, 11:45 PM UTC

   A fix has been implemented and we're monitoring search indexing.

3. resolved Mar 19, 2026, 02:15 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 12, 2026, 05:40 PM UTC· resolved Mar 13, 2026, 02:30 PM UTC

1. identified Mar 12, 2026, 05:40 PM UTC

   We are currently seeing errors from the Facebook API when attempting to publish video posts. As a result, video posts to Facebook may fail to publish. This appears to be an issue originating from Facebook’s API. We have contacted Meta and are monitoring the situation closely. Other Facebook post types (text and image) are functioning normally. We will share updates as soon as we receive additional information.

2. monitoring Mar 13, 2026, 10:38 AM UTC

   The issue affecting video post publishing to Facebook has been resolved. Facebook’s API is now operating normally, and video posts are successfully publishing again. We will continue to monitor to ensure stability.

3. resolved Mar 13, 2026, 02:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 04, 2026, 02:18 PM UTC· resolved Mar 04, 2026, 04:15 PM UTC

1. investigating Mar 04, 2026, 02:18 PM UTC

   We are currently investigating this issue.

2. investigating Mar 04, 2026, 02:25 PM UTC

   We are continuing to investigate this issue.

3. investigating Mar 04, 2026, 02:29 PM UTC

   We are continuing to investigate this issue.

4. investigating Mar 04, 2026, 02:45 PM UTC

   We have received reports from our ISP that they are experiencing an outage on our primary and backup links.

5. monitoring Mar 04, 2026, 03:21 PM UTC

   Our ISP appears to have remediated the issue. We will continue to monitor the situation.

6. resolved Mar 04, 2026, 04:15 PM UTC

   This incident is resolved.

7. postmortem Mar 09, 2026, 01:01 PM UTC

   ### Summary From approximately 9:08 EST to 10:15 EST on March 4, 2026, the US Customer Portal, Management API, and Scan API were unavailable. ### Root Cause The incident was caused by an outage of the ISP for both our primary and backup links. ### Remediation The incident was resolved when our ISP remediated the issue.

Read the full incident report →

Started Mar 02, 2026, 08:59 PM UTC· resolved Mar 03, 2026, 12:21 PM UTC

1. identified Mar 02, 2026, 08:59 PM UTC

   We're investigating reports of delays in sending Reviews notifications.

2. identified Mar 02, 2026, 10:45 PM UTC

   We identified an issue that delayed Reviews Analytics notifications beginning February 25. We’re working to send the delayed reports as soon as possible.

3. monitoring Mar 02, 2026, 11:07 PM UTC

   We’ve verified that Reviews Analytics notification emails are functioning normally again, including correct image attachments. We’re continuing to send any missed notifications and delayed reports from the impact period. We’ll continue to monitor and perform additional checks to ensure notifications and reports are delivered as expected. This issue is now mitigated.

4. monitoring Mar 03, 2026, 08:45 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Mar 03, 2026, 12:21 PM UTC

   We’ve verified that Reviews Analytics notification emails are functioning normally again, including correct image attachments. All eligible missed notifications and delayed reports from the impact period have now been successfully sent. This applies exclusively to reports with a sending frequency greater than daily (e.g., weekly or monthly), as daily reports were not reissued. The system is fully operational, and we’ve completed additional monitoring and validation to ensure notifications and reports are being delivered as expected. This issue is fully resolved.

Read the full incident report →

Started Feb 25, 2026, 04:09 PM UTC· resolved Feb 26, 2026, 01:20 AM UTC

1. investigating Feb 25, 2026, 04:09 PM UTC

   We are investigating reports that incorrect profile changes are appearing in Supervision and to end users. Our team is actively looking into this and will share updates as soon as they are available.

2. identified Feb 25, 2026, 04:40 PM UTC

   We have identified the cause of the profile mismatches and confirmed that the issue is no longer ongoing. Our team is now working on cleaning up any alerts or profile change requests that were generated as a result. We will continue to monitor the situation to ensure everything is functioning as expected.

3. identified Feb 25, 2026, 06:53 PM UTC

   All profiles have been reprocessed, and updates are now flowing through the system. Data will continue to refresh as synchronization completes.

4. monitoring Feb 26, 2026, 12:33 AM UTC

   All profiles have now fully synchronized, and profile data is up to date across the system. We will continue to monitor to ensure everything remains stable.

5. resolved Feb 26, 2026, 01:20 AM UTC

   This incident has been resolved.

6. postmortem Feb 27, 2026, 10:06 PM UTC

   ## **Summary** On February 25, 2026, at **13:39 UTC** we implemented a configuration change that enabled caching on a shared system component supporting our social crawling and publishing services. The caching was not configured to clearly separate data by account and request. As a result, in some cases the system reused previously stored responses for the wrong account, which led to certain data being saved under an incorrect account. At no point during this incident did unauthorized actors gain access to client or user accounts, nor were any changes initiated by unauthorized actors. At **14:37 UTC** on February 25, 2026, we reverted the caching configuration, which immediately stopped the incorrect behavior. We then conducted remediation activities to correct affected data and remove any erroneous records. ## **Customer Impact** During the incident window, customers may have experienced: * **False Supervision alerts** showing profile changes that did not occur, and in some cases profile information associated with other accounts was displayed. Yext dismissed all false alerts but in the Supervision UI the status may show as accepted. No action was taken on any of the alerts. * **A small number of inbound LinkedIn Direct Messages \(DMs\)** were temporarily saved under incorrect accounts. These DMs have been deleted from the incorrect accounts. * A subset of assets with **incorrect profile data display** that required recrawling to restore accuracy. ## **Data Privacy and Security** Based on our investigation to date: * **There is no evidence of permanent corruption** of source-of-truth systems. * For the mis-associated inbound LinkedIn DMs, our internal review did **not identify sensitive information exposure**. * The cross-account data mixing was **limited in scope and duration** and was addressed by disabling the caching configuration and completing cleanup and verification steps. * No content publishing functionality was impacted. * No posts were published to the wrong social networks. ## **Timeline \(UTC\)** * **13:39** Caching deployment initiated on VPC gateway infrastructure * **13:52** Caching became active * **14:37** Caching configuration reverted \(issue stopped\) * **16:55** Customer reports received indicating incorrect profile alerts * **17:16** Root cause confirmed as API Gateway caching returning improperly scoped responses * **Feb 26, 01:20** Incident marked resolved after remediation and monitoring completed ## **Root Cause** Caching was enabled on a shared system component that handles requests for multiple accounts. The caching rules were not configured to clearly separate data by account and request. As a result, in some cases the system returned previously stored information that belonged to a different account. Because downstream systems treated that information as valid, it led to incorrect alerts and actions being stored under the wrong account. ## **Mitigation and Recovery** We took the following actions: * Reverted the caching configuration to stop further incorrect responses. * Removed erroneous Supervision alerts from active queues. * Deleted mis-associated LinkedIn DMs from incorrect accounts. * Recrawled and restored affected profile data, followed by manual spot-check verification. * Removed or suppressed affected internal activity records created as a result of the incorrect context during the incident window. ## **Preventing Recurrence** We are implementing additional safeguards, including: * Stronger change controls for shared infrastructure, including enhanced review and risk assessment before enabling configuration changes that impact multiple accounts. * Stricter safeguards around caching behavior, including enforced separation of data by account and validation requirements before caching can be activated. * Expanded automated testing for shared gateway components to prevent cross-account data inconsistencies. * Improved monitoring and anomaly detection to identify and escalate cross-account data issues more quickly, including automated checks for alert accuracy and account-level data consistency.

Read the full incident report →

Started Feb 23, 2026, 02:45 PM UTC· resolved Feb 23, 2026, 04:50 PM UTC

1. investigating Feb 23, 2026, 02:45 PM UTC

   We are currently investigating this issue.

2. monitoring Feb 23, 2026, 03:27 PM UTC

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

3. resolved Feb 23, 2026, 04:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 22, 2026, 12:00 AM UTC· resolved Feb 22, 2026, 12:00 AM UTC

1. resolved Feb 23, 2026, 05:55 PM UTC

   We experienced delays in publishing Classic Pages content and degraded performance in the Pages platform from approximately 7:00 PM ET on Saturday, February 21 to 12:30 AM ET on Sunday, February 22. The issue has since been resolved.

Read the full incident report →

Started Feb 19, 2026, 05:09 PM UTC· resolved Feb 19, 2026, 07:49 PM UTC

1. investigating Feb 19, 2026, 05:09 PM UTC

   We are investigating reports of delays in Pages generation.

2. identified Feb 19, 2026, 05:43 PM UTC

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

3. monitoring Feb 19, 2026, 06:29 PM UTC

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

4. resolved Feb 19, 2026, 07:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 18, 2026, 05:00 PM UTC· resolved Feb 18, 2026, 07:24 PM UTC

1. investigating Feb 18, 2026, 05:00 PM UTC

   We are investigating reports of delays in Analytics metrics.

2. identified Feb 18, 2026, 05:17 PM UTC

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

3. monitoring Feb 18, 2026, 06:21 PM UTC

   We have deployed a fix for the delayed Analytics ingestion affecting Analytics Events and associated metrics. Most users should now see related Pages and Search metrics for the affected time period in the platform, though some metrics requests may continue to be cached across the next two hours. We will continue to monitor for any adverse effects.

4. resolved Feb 18, 2026, 07:24 PM UTC

   The issue affecting Analytics Events ingestion has been resolved. All systems are now operating normally. The issue began at February 16, 2026 at 6:00 AM EST and was resolved at February 18, 2026 at 1:21 PM EST. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Feb 06, 2026, 11:10 PM UTC· resolved Feb 07, 2026, 01:35 AM UTC

1. investigating Feb 06, 2026, 11:10 PM UTC

   We are investigating reports of delays in review submission. We will provide an update when have further information

2. identified Feb 06, 2026, 11:32 PM UTC

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

3. monitoring Feb 06, 2026, 11:51 PM UTC

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

4. resolved Feb 07, 2026, 01:35 AM UTC

   This incident has been resolved.

Read the full incident report →