Yext Status Page

Jun 11, 2026 · resolved Jun 12

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.

Jun 4, 2026 · resolved Jun 4

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

Jun 3, 2026 · resolved Jun 3

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.

Jun 2, 2026 · resolved Jun 3

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

Jun 3, 2026 · resolved Jun 3

This incident has been resolved.