Yext outage history

We have deployed a fix after identifying issues accepting events via the Events API in the US. Events are being accepted again, and we are monitoring to ensure stability.

The issue affecting the Events API in the US has been resolved. All systems are now operating normally. The issue means that events sent to the API may not have been recorded for the span of time from 7:34pm to 7:48pm EDT.

We are Investigating Reports of Problems with Ask Scout in the EU Partition

We have mitigated the issue and Ask Scout threads are working in the EU.

This incident has been resolved.

We are currently investigating an issue affecting portions of the Hearsay web application. Some users may experience intermittent failures when navigating or interacting with certain areas of the web interface. The impact is limited to the web UI. Mobile applications, Salesforce integrations, and all backend data processing continue to operate normally.

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

This incident has been resolved.

Semantic search functionality in Yext Search had elevated error rates in our EU regions from 6/29/2026 from 12 AM to 4 AM. Semantic search functionality has since been resolved.

We identified elevated error rates in our Analytics systems, affecting the Analytics tab in the customer portal, some Scout functionality, and other Analytics-related functionality across the customer portal. We have implemented a fix, and Analytics requests are currently being served as normal. We are continuing to monitor to ensure stability.

This incident is resolved.

In the EU production environment, the Analytics section of the customer portal and the Analytics API experienced elevated error rates from 2026/06/22 9:23 PM UTC until 2026/06/23 9:04 AM UTC. Our engineering team has implemented a fix, and has added additional safeguards to prevent recurrence of similar issues in the future.

We found an issue that caused our "Connect to Google/Yelp/Facebook" Optimization API tasks to not be returned from May 12, 2026 ~3:00 PM EST to June 11, 2026 7:30 AM EST. We have resolved the issue, and expect these tasks should be properly returned in the API for all customers now.

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.

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

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.

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.

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.

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.

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.

This incident has been resolved.

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.

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

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.

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

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.

LinkedIn has implemented a fix and we are monitoring results.

This incident has been resolved.

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

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

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

This incident has been resolved.

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

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

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

This incident has been resolved.

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

This incident has been resolved.

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

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

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.

This incident has been resolved.

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.

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

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

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

This incident has been resolved.

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.

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

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

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.

This incident has been resolved.

We are investigating reports of a partial outage in Analytics API

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

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

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

This incident is resolved.