Is Yext Down Right Now? Check if there is a current outage ongoing.

Between the time of approximately 2:20 pm and 4:30 pm EST, some portion of Search queries were intermittently timing out and not returning results.

From June 4th at 12:09pm EST through June 10th at 12:38pm EST email and in-platform review notifications for Google reviews were not sent out due to a configuration issue. A fix has been deployed and going forward review notifications for new and updated Google reviews are sending as expected. Review Notifications that should have been sent during the affected time period will be sent out over the next 24-48 hours.

From 4:00pm EST to 4:46pm EST most requests to the Management API's Reviews endpoints failed due an incorrect software configuration. The underlying issue has been addressed and the API is now working as expected. Calls that attempted to write data during the window and received and error response did not succeed and should be retried.

We found an issue with our scanning backend that is causing all Listings scans originating from the Partner Scan, Scan API, and Scout to fail. We are resolving the issue and should have functionality restored within the next 30 minutes.

We discovered an error that caused a small number of locations to experience a delay pulling in Reviews from our publisher network from Monday May 26, 5:15AM ET until Tuesday June 3, 3:00PM ET. We have since fixed the error and confirmed new Reviews scans have been kicked off for all the affected locations.

This incident is resolved.

We are continuing to monitor for any further issues.

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

We have identified the source of errors and are working on remediation.

We are investigating reports of errors in Classic Pages Generation for sites that use Enhanced Content List data.

This incident is resolved.

We are continuing to monitor for any further issues.

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

We have identified the source of errors and are working on remediation.

We are investigating reports of errors in Classic Pages Generation for sites that use Enhanced Content List data.

From 1:00AM EDT to 9:45AM EDT on May 30, 2025, developers using the Pages system may have experienced errors creating new deploys. The underlying issue has been mitigated and any new deploys made after 9:45AM should no longer be affected by this error. Page generation for existing deploys was unaffected during this period.

From 1:00AM EDT to 9:45AM EDT on May 30, 2025, developers using the Pages system may have experienced errors creating new deploys. The underlying issue has been mitigated and any new deploys made after 9:45AM should no longer be affected by this error. Page generation for existing deploys was unaffected during this period.

This incident has been resolved.

We have remediated the issue, and are processing the delayed generations. We will continue to monitor the situation.

We are investigating reports of delays in Classic Pages generation.

This incident has been resolved.

We have remediated the issue, and are processing the delayed generations. We will continue to monitor the situation.

We are investigating reports of delays in Classic Pages generation.

This incident is resolved.

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

We are investigating reports of errors in the Portal and Management APIs.

This incident is resolved.

We are continuing to monitor for any further issues.

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

We have identified the issue and are working on remediation.

We are investigating reports of delays in Pages generation. Pages serving is not affected.

# **Summary** ‌ Starting around 5:30PM ET on April 24th, 2025, approximately 4% of calls to Yext’s Management API failed to complete. This, in turn, led to downstream errors in certain reseller flows and custom dashboards, although no data was lost or corrupted. By 5:30AM ET on April 25th, the underlying issue was resolved, and service was restored to normal. ‌ # **Root Cause** ‌ The issue was caused by a configuration change to Yext’s Users API, a subset of the management API,  as part of an ongoing migration to a new service framework. An incorrect deployment of this change led to issues during call routing from our API gateway, which led to errors for the subset of calls to this backend. ‌ # **Remediation** ‌ The configuration change was rolled back, and the services redeployed, which restored them to full functionality. Going forward, we will add extra synthetic monitoring for the Management API to better catch this category of issue and add custom error routing for this type of gateway-backend communication.

This incident has been resolved.

A fix has been implemented and we are monitoring the results

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

We are currently investigating reports of errors for a subset of our Management API calls, which is also affecting some custom customer dashboards.

A bug was introduced at 4pm on April 23rd, 2025 that prevented customers from responding to reviews for a subset of entities until 10am on April 24th.

This incident is resolved.

We have remediated the issue, and are processing the delayed data. We will continue to monitor the situation.

We have identified the issue and are working on remediation.

We are currently investigating this issue.

# **Summary** From 12:57PM ET on Thursday, March 13, 2025, until 3:29PM ET on Thursday March 20, 2025, Yext needed to pause the export of data to Google Listings. This action was required to prevent our customers’ GBP entities from incorrectly requiring re-verification on Google due to problems discovered in Google’s system. Because of the exporting pause, it is possible that some entities’ Google listings were not updated for the duration of this incident. # **Root Cause** The root cause was a change introduced by Google that caused a large number of previously cleared updates to Listings content to require re-verification of the entity on Google. Since the re-verification process can be tedious and time-consuming for our customers, Yext proactively decided to pause Listings exporting to Google until our monitoring indicated the problem was resolved. When Yext re-enabled the exporters at 3:29PM ET on Thursday, March 20, 2025, we observed standard rates of listings entering a re-verification status. As such, we felt comfortable leaving Google exporting on to catch up on the backlog of updates that formed throughout the week. At 3:57PM ET on Friday, March 21, 2025, the backlog was fully processed, and all listings were restored to an ongoing sync state. # **Remediation** We communicated with our customers during the incident through Trust Site updates, an in-platform banner, and direct correspondence. We also maintained constant communication with Google to ensure we understood their latest attempts to resolve the issue. This allowed us to turn the Google Listings exporters back on as quickly as possible. Going forward, we are working on better transparency by alerting our customers directly in our platform for these publisher-related issues. This will allow customers to stay up-to-date with the latest publisher information and have the best information available to handle these outages.

This incident has been resolved.

Our monitoring continues to show that Google Listings exporting is behaving as expected. We have finished processing the backlog of updates generated throughout the last week; we're going to keep an eye on the system to make sure those updates don't result in any new problems.

Google deployed another fix this morning and has provided us with the green light to resume our listings sync. We have been closely monitoring the situation, and all indications suggest that things are back to normal. We will continue to closely monitor the situation and will provide further updates here if necessary. Thank you for your patience and trust as we work to ensure everything runs smoothly.

Earlier today, Google acknowledged the issue in this post (https://support.google.com/business/thread/332226114). However, despite the initial fix, we are still seeing a high rate of profiles getting flagged for verification and therefore will be leaving the sync turned off overnight while Google investigates the latest data. We will continue to update this incident as new information comes in.

We’re continuing to work with Google to resolve the problems we’re seeing. As of right now, the Google Listings exporters remain off.

Our monitoring continues to show an elevated number of Google Listings that require re-verification as exports have progressed, so we are disabling the exporters again. We will continue to work with Google to get the issue resolved, and will provide updates as we work through issues with them.

We have received communication from Google that more issues have been resolved on their end; as such, we have re-enabled Google Listings sync and will continue to monitor our systems for any issues. We will update throughout the day if we notice any more problems.

After several hours of monitoring, we are still seeing an unusually high number of Listings getting flagged for re-verification on Google. As a precaution, we have paused Google Listings sync overnight while Google reviews the latest data. We will share updates as soon as we receive more information from Google.

We have increased the rate of our Listings exports to Google and things continue to look okay. We will continue monitoring for a few hours to ensure the system continues to behave as expected.

Earlier today, we received guidance from Google that it was safe to resume Listings Delivery; as such, we have re-enabled it and are closely monitoring the situation to confirm everything is behaving as expected.

Following Google's fix deployment, we are still observing a higher-than-expected rate of profiles being flagged for re-verification. As such, Google has recommended keeping the Listings sync off through the weekend. Google is actively working to transition impacted profiles back to a Verified status. We will continue monitoring the situation and provide further updates as we receive them.

We have received guidance from Google that a fix has been deployed, and we are now in the process of testing it.

Google’s technical support team is actively investigating the issue, and we are working closely with them on a fix.

We are continuing to investigate this issue.

We are investigating reports of increased re-verification counts across Google listings. As a result, we have temporarily paused exports to Google. We have opened a thread with our contacts at Google and are actively troubleshooting on our side as well.

This incident is resolved.

We have remediated the issue, and are processing the delayed data. We will continue to monitor the situation.

We are currently investigating this issue.

# **Summary** Starting around 10:00 PM ET on March 17, 2025, updates to Yext entities with the “Geomodifier” field began experiencing an increase in error rates. This caused an increase in downstream errors in Pages generation, API calls, and ETLs. The issue was resolved by 7:00 AM ET on March 18, 2025, and error rates returned to normal. No existing data was lost during this incident. # **Root Cause** The root cause was the accidental disablement of a product feature during upgrades to our product feature system. Since this feature controlled access to the “Geomodifier” field, this disablement caused errors and incorrect display behavior when updating or viewing profiles using this field.  # **Remediation** The issue was resolved by re-enabling the relevant product feature. Going forward, we will implement new protocols controlling the use and disablement of product features and build new classes of controls specifically for profile field availability.

This incident has been resolved.

The issue has been identified and a fix has been made, and we are currently monitoring the results

We are investigating reports of a particular entity field, Geomodifier, to be unavailable, causing a partial outage in some downstream systems.

This incident has been resolved.

Snowflake is showing that their incident is resolved and our monitoring indicates things have returned to normal. We will monitor for any regressions and update if we find anything.

Our monitoring is showing a reduced error rate for the systems impacted by the Snowflake outage. We will keep monitoring the situation and update when everything is back to normal.

We have discovered several additional pages affected by this outage.

We're investigating higher rates of slow and failing analytics queries in the platform and API. We believe this is related to an ongoing Snowflake incident; more information can be found on their trust site: https://status.snowflake.com/incidents/9mwvw50z4wnm.

The issue has been identified, the fix has been implemented, and log ingestion has caught up. This incident has been resolved.

We are investigating reports of delays in Entity History Logs ingestion.

# **Summary** ‌On March 5, 2025, at approximately 7:00AM ET, Content API, Search, Knowledge Tags, and Pages started experiencing intermittent failures for a subset of customers. By approximately 9:30AM ET, service was restored to almost all customers, and by 11:00AM it was restored to all customers. # **Root Cause** ‌The root cause was determined to be a distributed denial of service \(DDoS\) attack on a subset of our Content API resources. These attacks caused excessive load on particular shards of our backend data layer, causing requests to those specific shards to experience high latencies and timeouts. This, in turn, caused a partial outage in Content API, as well as other Yext services that use Content API, including Search, Knowledge Tags, and Pages. # **Remediation** ‌While the system already has multiple layers of protection against denial of service attacks \(such as rate-limiting and caching\), we will implement additional defense mechanisms at both the CDN and backend levels to further neutralize this specific distributed attack vector. Additionally, we will investigate introducing further short-circuiting capabilities at the data storage layer to mitigate general sharp spikes in load.

This incident has been resolved.

The issue has been mitigated, and we are monitoring the results

We have identified the issue and have mitigated it for most customers.

We are continuing to investigate this issue.

We are investigating reports of a partial outage affecting Content API and Search.

This incident has been resolved.

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

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

We are investigating reports of errors in the Customer Portal

This incident is resolved.

We have remediated the issue, and will continue to monitor the system.

We are working to remediate errors in many AI-related features in the Yext platform.

This incident has been resolved.

We are currently investigating high error rates in the Analytics Queries system which is resulting in some customers seeing timeouts attempting to fetch analytics reports or pull analytics via our APIs.

From 9:48 to 10:18 EST this morning the Social admin UI was unavailable due to a transient issue.

A backup in saved filter processing delays in pages publishing, streams API updates and search indexing. This incident was resolved at 9:45AM EST today and all systems have returned to normal.

This incident is resolved.

We have remediated the issue, and will catch up on the delayed updates. We will continue to monitor the situation.

We are investigating reports of delays in Classic Pages publishing

This incident has been resolved.

We have resolved the issue and the affected systems are working as expected. Connectors is working through a slight backlog of tasks built up during the incident; we will keep an eye on things and ensure the system is catching up at an acceptable rate.

We have identified an issue that is making our Crawlers, Plugins, and Connectors systems unable to service requests. This is having an adverse effect on our Streams and Pages Generation features at this time.

This incident has been resolved.

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

We have identified an issue that is causing a delay in showing the most recent changes on the Entity History page in the platform.

The Yext Search logs system was partially degraded between 3:55 PM EST and 8:45 PM EST on 1/28/2025; during this time, some Search logs were lost due to an issue in our system.

This incident is resolved. Between 17:14 Wednesday EST and 01:16 Thursday EST, there were intermittent problems capturing Analytics events, Chat logs, Content API logs, and Plugin logs. Metrics and logs for those systems may be missing a portion of events from the affected period.

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

We are investigating reports of errors in Analytics Ingestion.

This issue has been resolved. Please contact your CSM or implementation team if you are continuing to see issues with your holiday hours populating correctly in Pages.

Sites using an outdated pages component may incorrectly calculate store holiday hours. This issue only affects customers viewing the page from a different time zone than the store's location. For users in the same time zone as the location, the open status and holiday hours will be correct. To resolve this, update your site to use the HoursStatus component from @yext/pages-components instead of @yext/sites-react-components.

This incident is resolved.

We have remediated the issue, and are processing the delayed data. We will continue to monitor the situation.

We are currently investigating this issue.

This incident is resolved.

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

This incident has been resolved.

We are investigating reports of timeout errors in Customer Portal.

This incident has been resolved.

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

We have identified the issue and failed over the impacted serving regions. Error rates are returning to normal in production. Sandbox search serving remains offline.

We are seeing high error rates in production and an outage in sandbox, we are working to put a fix in place. Other APIs appear to be operating normally

We are investigating reports of errors in Search Serving.

This incident is resolved.

We have successfully retried all failed posts and are no longer seeing any issues with the Facebook API. We will continue to monitor the situation.

Unexpected maintenance on the Facebook API Platform resulted in errors posting to Facebook between 12:55pm and 1:20pm EST. The API appears to have stabilized and we will continue to monitor the situation. We are currently looking into the failed social posts during that time period to determine how to get them re-posted. Listing deliveries and Review Scans will automatically retry.

# **Summary** For intermittent periods of time between 11/25 - 11/27, customers saw scan failures in both the API and the Scan tool. On 11/25, errors were seen from approximately 6:30PM ET until 7:50PM ET. On 11/26, errors were seen over 3 small periods, totaling approximately 45 minutes. On 11/27, errors were seen from approximately 3:15AM ET until 6:00AM ET and then again approximately from 4:00PM ET until 4:50PM ET.  # **Root Cause** A network file share system was experiencing issues resulting in the need to failover to a backup. This occurred on 11/25, starting at approximately 5:00PM ET.   The backup system experienced a series of issues resulting in the server becoming unresponsive and crashing between the evening of 11/25 and the afternoon of 11/27. The degraded state of the backup system led us to fail back to the primary on the afternoon of 11/27, starting approximately at 4:00PM ET.  # **Remediation** To prevent similar issues from occurring again, we will remove the existing dependency on the shared file system for the Scanning system. Additionally, we are adding telemetry to notify us more quickly if the scanning system experiences similar problems in the future.

This incident has been resolved.

We have identified a system that was failing intermittently. We have taken steps to resolve it and are now monitoring.

We are investigating reports of degraded performance. We are investigating which systems are impacted and will provide an update.

This incident is resolved, all previously delayed updates have been processed.

We have remediated the issue, and are processing the delayed updates. We will continue to monitor the situation and report when all delayed updates have been published.

We are responding to reports of delays in Pages publishing for the US source region and working on remediation

This incident is resolved.

The delayed updates have been processed. We will continue to monitor the situation.

We have remediated the issue, and are processing the delayed updates. We will continue to monitor the situation.

We have identified the issue and are working on remediation.

We are investigating reports of delays in Pages publishing for the US source region

We have confirmed that all customers have remained caught up and no further problems have occurred since our fix yesterday.

Our fix is in place and nearly all customers are fully caught up, we are continuing to monitor recovery for the remaining customers.

We have identified the cause of the delay and are working on implementing a fix

We are continuing to investigate this issue.

We are experiencing delays in making content updates available to Pages Generation and our Consumer APIs

Pages generation has been in a normal state for over 18 hours and we have not detected any further issues.

We have identified the issue and put in place a fix, we are monitoring closely to ensure everything is working properly.

We are investigating reports of publish failures for some customers.

This incident has been resolved.

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

We have identified an issue that is preventing users from logging in or changing their password on the Yext Hitchhiker Site.

# **Summary** On October 29th, 2024, at approximately 3:00PM ET, the Customer Portal experienced an outage for nearly two hours. Some remaining errors remained for the subsequent 2.5 hours, and the portal was returned to an error-free state by approximately 7:45PM ET. At that point, some translations were unavailable. By 10:00PM ET, the translations were fully restored. # **Root Cause** Our front-end web services depend on language translation files to serve the Customer Portal in various languages. These files are hosted on a legacy storage system, and that storage system had become desynchronized with the application servers that utilize them. This caused slowness when accessing these files. The slowness caused a cascade of issues that ultimately resulted in the Customer Portal being unable to start. ‌ To remediate this issue, the entire fleet of application servers had to be restarted in a rolling fashion. This was time-consuming, leading to the protracted downtime. # **Remediation** Prior to this incident, we had already begun deprecating the legacy storage system and had migrated many workloads off it. We will redouble our efforts and prioritize migrating these translation files to the new architecture. ‌ Additionally, we have added telemetry to notify us more quickly if the legacy storage system experiences similar problems in the future. ‌ Lastly, we have refined the process for restarting our fleet of application servers so that we can recover more quickly in the worst-case scenario.

This incident is resolved.

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

We have identified the source of errors and addressed the underlying issue. The customer portal is operational at this time. Translations for non-English languages may be missing from the portal, we are working to restore them.

We have largely remediated the customer portal issues. A small subset of errors are still being worked on towards resolution.

We are continuing to investigate this issue.

We are currently investigating reports of an outage within our customer portal.

We are investigating reports of errors in Partner Scan

This incident is resolved.

A fix has been implemented, data is caught up, and we are monitoring the results.

We have identified the issue and are working on remediation. Updates in Content/Knowledge Graph are working as excepted, this only affects history logs.

This incident has been resolved.

We have implemented a fix and Listings Publishing updates are flowing through the system again. We have a small backlog to clear from the past 7 hours, so we will keep an eye on the system and update when everything is caught up.

We have identified an issue with our Listings Publishing system that has prevented entity updates from reaching our Publisher network since around 3:00 AM EST earlier today.

We have finished our data repair work and believe Search Tracker functionality is properly restored for all entities.

We have started a migration to repair the data issues and restore Search Tracker functionality to all entities. We expect this to be completed by tomorrow; we will continue to update as the migration work proceeds.

We have resolved the primary issue in Search Tracking and will continue to monitor the system. We are continuing to resolve some data issues with a smaller number of affected entities, and will update as we work through those issues.

We have identified the issue and are working on remediation.

We are investigating an issue causing Search Tracker to be missing data for some entities starting on the 4th of September.

This incident is resolved.

We have remediated the issue, and are processing the delayed data. We will continue to monitor the situation.

We are investigating reports of delays in Connectors and Chat Log Data.

This incident is resolved.

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

We have identified the source of errors and are working on remediation.

We are investigating reports of errors in the Management API for the US Partition

This incident is resolved.

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

We have remediated the problem for all but a couple accounts. We are continuing to work on a resolution for those customers.

We have identified the issue and are working on remediation.

We are investigating delays in our streams system, which affects new deploys and data updates in Pages, Content API, and Search.

This incident is resolved.

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

We have identified the issue and are working on remediation.

We are investigating login failures to our sandbox environment

This incident has been resolved.

We have identified an issue in a specific node in our serving cluster and removed the node from the cluster. We are confirming that serving has returned to normal for search responses while we continue to resolve the underlying issue.

We are investigating reports of no results being returned from some EU customers.

Between 10/10 8:24 PM and 10/11 4:48AM Eastern Time, certain pages for Resellers in Partner Portal were unable to load.

This incident has been resolved.

The missing Analytics data has been restored, and we've deployed a fix to address the root cause. We'll continue to monitor the situation.

The team is continuing to run through the recovery procedure to restore missing Analytics data.

We are currently running through the recovery procedure to restore missing Analytics data.

We have prepared the scripts necessary to restore the missing data, but we are planning to run the recovery starting in the morning, US Eastern Time, to ensure that its operation can be appropriately monitored. Our next update will be tomorrow morning, US Eastern Time.

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

We are investigating reports of missing Analytics data for a small subset of customers.

This incident has been resolved.

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

We are investigating reports of errors in Entity Search in EU environment.

This incident has been resolved.

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

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

We are investigating reports of errors in Sandbox Customer Portal.

This incident is resolved.

We have remediated the issue, and the delayed data has been processed. We will continue to monitor the situation.

We have identified the issue and are working on remediation.

We are investigating reports of delays in showing Search Logs in the portal.