Is Yext down?

We experienced elevated errors affecting Analytics, Search, Pages, Live API, and Streams API services hosted in our EU environment. During this disruption, users may have encountered errors loading pages, retrieving search results, or making API requests. Traffic has been restored to the affected infrastructure, and services are recovering. Our team is monitoring to confirm continued stability. We will provide another update once the incident is fully resolved.

On October 27, 2026, from approximately 4:00 p.m. to 4:20 p.m. EDT (20:00–20:20 UTC), services hosted in our EU environment experienced elevated errors affecting Search, Pages, Live API, Streams API, and Analytics event collection. Users may have encountered errors loading pages, retrieving search results, or making API requests. Some analytics pixel events were not collected during the disruption. Traffic was restored to the affected infrastructure, and subsequent monitoring confirmed stable operation. We apologize for the disruption. We will share a post-incident review with additional details about the cause, impact, and steps we are taking to reduce the risk of recurrence.

On October 20, some customers in our EU region experienced errors when making Knowledge Graph updates, delays in Pages publishing, and saved filters that did not reflect recent changes. Our monitoring detected the interruption at 08:29 UTC (4:29 a.m. EDT). A database server supporting these services became unresponsive. Our on-call engineers restarted the server and restored its normal read/write configuration, allowing affected services to recover. Core API and data-freshness checks confirmed recovery by 09:16 UTC (5:16 a.m. EDT). The service interruption has been resolved. Our engineering team is reviewing the event and identifying improvements to strengthen service resilience and recovery. We apologize for the disruption and appreciate your patience.

From 10:50 AM EST until 12:15 PM EST on October 14th, 2026, Report Builder was unavailable for some clients due to an error in the Analytics system. The issue was resolved and no further issues were discovered throughout the day.

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.

We are currently investigating an issue affecting inbound voice services for a subset of users. Impacted users may experience issues receiving inbound calls. Our engineering team is actively investigating the cause and working to restore normal service as quickly as possible. Outbound voice services are not currently known to be affected. We will provide another update as more information becomes available.

A fix has been deployed to address the inbound voice issue affecting a subset of users.

This incident has been resolved.