Yext had 61 outages in the last 2 years totaling 209h 35m of downtime — averaging 2.5 incidents per month.
There were 61 Yext outages since September 12, 2025 totaling 209h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently experiencing delays in processing Expert Services ETLs.
Our ETL system has recovered, the issues were related to the ongoing Amazon Web Services incident. We are monitoring progress on running ETLs.
All ETLs are behaving normally
We are investigating reports of elevated error rates in the Scout Real Time Scan API.
The ongoing Snowflake Incident is causing impacts on the Yext Analytics platform and systems that rely upon it, such as the Scout Interactive API. https://status.snowflake.com/incidents/gvmvnx7lyxjj We are monitoring Snowflake's ongoing incident and will provide updates as we can.
Our automated monitoring checks have recovered. We are continuing to monitor Snowflake's status for updates. Some analytics queries may still be slower than usual.
We are continuing to monitor system performance as a result of the ongoing incident with Snowflake
This incident is resolved.
We are currently investigating this issue.
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.
Due to an outage of our model hosting provider, Yext Search and Reviews experienced a period of partial degradation. The downstream issue has now been mitigated and service has been restored.
This incident has been resolved
We are investigating reports of delays in updates to the Knowledge Graph being reflected in Entity Search and Live API.
The issue has been identified and a fix is being implemented.
The issue has been mitigated. Entity Search and Live API are now reflecting updates normally. We will continue monitoring the situation.
This incident has been resolved.
The Chat Intent Insights page is currently failing to generate new clusters. We've identified the issue and working on a fix.
This incident has been resolved.
We have identified a partial outage affecting Analytics Events. Events sent to the realtimeanalytics.yext.com domain encountered errors and were not ingested to the Yext Platform. We have deployed a fix and all systems are now operating normally. The issue began at 7:27pm UTC and was resolved at 7:47pm UTC.
We are currently investigating this issue.
We have identified the source of errors and are working on remediation.
We have remediated the errors. We will continue to monitor the situation.
This incident has been resolved.
# **Summary** From approximately 3:30 PM PT to 3:58 PM PT on October 2, 2025, the Hearsay web and mobile applications were unavailable. During this time, users were unable to log in or perform actions across Social and Relate. # **Root Cause** The outage was caused by an issue that occurred during a routine database update. This process unintentionally disrupted communication between core services that support the Hearsay application. # **Remediation** The issue was resolved by restarting the affected systems to restore normal connectivity and service operation. To prevent similar occurrences, we have improved our internal database update process to include additional safeguards and verification steps, and will continue to ensure such changes are performed outside of business hours.
Some number of Yext listings for new customers are stuck in the Processing state for longer than expected due to a problem in the system. We have identified the root cause, and are working through getting those listings delivered to our publishers as soon as possible.
We are continuing to work on syncing all the affected listings.
We have cleaned up the affected listings and ensured that anything incorrectly stuck in a Processing state is now synced to the publisher network. We will keep an eye on the system for any regressions.
This incident has been resolved.
We are investigating reports of issues with redirects in Classic Pages
We have remediated the issue. We will continue to monitor the situation.
This incident is resolved.