Major incident

Yext: Incorrect Search Autocomplete Suggestions for Experiences using Legacy Search Endpoints

Current status of Yext: Operational — live Yext status

Timeline

1. Sep 9, 2026, 16:00 UTC
   resolved
   From September 9 at approximately 12:10 p.m. EDT through September 16 at 10:13 a.m. EDT, some customers may have received autocomplete suggestions that did not correspond to their submitted queries. A cache configuration issue caused query parameters, including the search input and search experience, to be omitted from the cache key for a legacy Search API endpoint. Consequently, an autocomplete response cached for one request could be returned for a different query or Search experience. The issue was limited to autocomplete requests from older frontend implementations using the legacy endpoint. Standard autocomplete requests using current endpoints were not affected, and our investigation found no evidence of meaningful customer-facing impact to search results. We corrected the cache configuration at 10:13 a.m. EDT on September 16 and verified the expected behavior within minutes. We are evaluating additional monitoring and configuration validation to help detect and prevent similar issues.

Updates as published by Yext (original).