Yext outage history

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.

We are seeing degraded performance with some areas of the Hearsay application. We are actively investigating and will update shortly.

We are continuing to investigate this issue.

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

This incident has been resolved.

We are currently investigating this issue.

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

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

This incident has been resolved.

# Summary On August 17, 2026, users were temporarily unable to access Yext through [my.hearsaysocial.com](http://my.hearsaysocial.com) for approximately 12 minutes, from 11:20 AM to 11:32 AM ET. No customer data was lost, and this was not a security incident. # Root Cause A content library indexing process generated higher-than-expected system demand, temporarily causing service requests to fail and affecting access to Yext through [my.hearsaysocial.com](http://my.hearsaysocial.com). # Remediation We increased system capacity to complete the rebuild and restore normal service. To prevent recurrence, we are updating the indexing process to apply smaller, incremental changes rather than requiring a full rebuild. We are also making database performance improvements to support more reliable processing during these updates.

We have identified an ongoing GitHub service incident that is causing delays for some Yext Pages publishes and resulting in degradations in the platform. Publishing requests may take longer than expected to complete. We are monitoring GitHub’s recovery and will provide an update as more information becomes available.

Github has mitigated the issues affecting Pages publishing and the portal. Service has been fully restored. We will continue to monitor the situation.

This incident is resolved.

We are investigating reports of delays in Pages Publishing in the EU.

We have identified the issue and are working on remediation.

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

This incident is resolved.

This incident has been resolved.

We are aware of login issues affecting the Hearsay for Intune by Yext iOS application. We are working on a fix and will update as we have more information.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring results. Users of our Intune iOS application should update to the latest version, 9.5.2.

This incident has been resolved.

Advanced functionality, like Search's Extractive QA or semantic search, was degraded for a subset of customers between 2 AM and 4:30 AM this morning. Functionally was fully restored after 4:30 AM.

File assets are failing to load in customer accounts

A fix has been implemented and we're monitoring the results

We are continuing to monitor for any further issues.

This incident is resolved.

This incident was related to [https://www.yexttrust.com/incidents/vflk2wb46qj3](https://www.yexttrust.com/incidents/vflk2wb46qj3), please view the full postmortem there.

New Pages deployments are currently failing due to an outage with our repository provider, Github. We are monitoring their status at https://www.githubstatus.com/

We are observing restored functionality but will continue monitoring as the Guthub incident is still ongoing

This incident is resolved.

A subset of images are failing to load on our customer's Pages and Search responses.

We are still investigating the image loading failures and are working with our CDN provider to assess the issue

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

This incident is resolved.

# **Summary** On July 16, 2026, a change made by a third party vendor, Cloudflare, caused a portion of dynamically resized images to fail intermittently across a subset of Yext-hosted customer experiences in our U.S. based production environment. Specifically, this included images and files served on our [mktgcdn.com](http://mktgcdn.com) domain. These are used widely across Yext’s Pages and Search products. The initial incident affected image requests starting 11:00AM ET and was resolved at 7:49PM ET. Roughly 11% of image serving requests were affected. The remediation for the initial incident exposed a separate routing gap affecting a smaller set of hosted file assets. This less severe follow-on issue began when the initial remediation was deployed on the evening of July 16 and was resolved by 6:33AM ET on July 17. Normal service has been restored. No customer data was lost or corrupted, and no action is required from customers. # **Root Cause** Cloudflare made an internal change that altered how a legacy routing configuration interacted with the request processing services Yext uses for image delivery. As a result, some dynamic image requests followed an incorrect processing path and returned content that could not be interpreted as an image. This produced intermittent image loading failures. A large subset of requests including those already cached by Cloudflare could continue to succeed, which made the impact inconsistent across requests. To restore image delivery, Yext migrated the affected routing configuration from Cloudflare’s legacy rules system to its current rules system. The initial replacement did not include a fallback route that was still used by a smaller set of non-image file assets. Those assets returned errors until the missing routing behavior was restored the following morning. # **Remediation** Yext restored dynamic image delivery by migrating the affected routing configuration to Cloudflare’s current rules system, clearing affected caches, and verifying that both cached and uncached image requests succeeded. We subsequently restored the missing route for the smaller set of affected file assets and confirmed that those assets were loading normally. To reduce the likelihood and impact of similar incidents, Yext is: * Continuing to migrate remaining legacy Cloudflare routing rules to the current rules system. * Improving monitoring and alerting for elevated image and file-delivery failure rates so intermittent problems can be detected sooner. * Expanding tracing and diagnostic capabilities for image serving requests handled through Cloudflare. * Reviewing and removing remaining dependencies on legacy storage and fallback routing paths. No temporary customer workarounds remain in place, and customers do not need to take any action.

We are investigating indications of an increased error rate in the Events API in the US partition.

A workaround has been implemented and the Events API is now accepting events once again. We are working to resolve the underlying issue.

We have identified the source of intermittent latency increases in the Events API in the US partition. We have taken some measures to help alleviate the problem and are working on a full resolution.

The measures we have taken to help alleviate the problem are having some benefit and more events are being accepted. We continue to work on resolving the underlying cause.

We have resolved the underlying issue, and in the past six hours of monitoring, the issue has not reoccured. The Events API is operating normally now. The issue intermittently impacted requests to the Events API between 12:37 AM to 1:11 PM EDT.

We are investigating reports of errors in Hearsay Platform.

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

We are continuing to implement the fix and will provide another update as soon as more information is available.

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

This incident has been resolved.

# **Summary** On July 16, 2026, users were unable to access Yext via [my.hearsaysocial.com](http://my.hearsaysocial.com). The disruption began at 8:43 AM ET and was resolved at 9:56 AM ET, resulting in a total impact duration of approximately 73 minutes. APIs and automated integrations were not affected, and no customer data was lost or at risk. # **Root Cause** An infrastructure change caused the authentication service to be unable to access the configuration it needed to function, preventing user logins. Because many platform features depend on the authentication service, this failure propagated beyond login itself and caused errors across most of the application.  # **Remediation** Our team identified the cause of the incident and restored service by reverting the infrastructure change. Service was fully restored at 9:56 AM ET. A permanent fix has since been implemented, and no temporary workarounds remain in place. To prevent recurrence, we are \(1\) improving our pre-production validation of infrastructure changes to confirm required configuration is in place before deployment, \(2\) updating the authentication service to degrade gracefully rather than fail completely when configuration is unavailable, and \(3\) strengthening our rapid-rollback process and exercising it on a regular basis.

We have identified an issue that is delaying Listings updates since Tuesday July 14th, 11:17 PM EST. We have implemented a fix to resume these updates, but the queue will take some time to become current; we will update as the system catches back up.

The queues are about halfway through catching up; we will continue to provide updates as the system returns to normal behavior.

This incident has been resolved.

We are investigating reports that the reviews-related pages in the Customer Portal are unavailable.

We identified the issue, implemented a fix, and restored service to reviews-related pages.

We will continue to monitor the system closely and develop additional preventative measures.

This incident has been resolved.

# **Summary** On July 14, 2026, an error caused a service disruption that prevented customers from viewing reviews, responding to reviews, generating review responses in the Customer Platform UI, and managing review responses through the Management API. The disruption began at 5:43 AM ET, was detected by automated monitoring at 5:48 AM ET, and was resolved at 6:13 AM ET, resulting in a total impact duration of approximately 30 minutes. # **Root Cause** A service update introduced support for a new review response integration. This update was the first to depend on an internal configuration that had not yet been established for the affected service, causing that service to fail during startup. Because certain related services lacked certain fallback behavior, the failure propagated beyond the new integration itself and caused both the review monitoring and review response pages in the Customer Platform UI, as well as review response management through the Management API, to return errors. # **Remediation** Our team identified the cause of the incident and restored service by reverting the update that introduced the issue. Service was fully restored at 6:13 AM ET. A permanent fix has since been implemented, and no temporary workarounds remain in place. ‌ To prevent recurrence, we are \(1\) isolating integration-specific failures so that a single unhealthy integration cannot disrupt these pages, \(2\) adding graceful fallback behavior so the pages remain usable when a single capability is unavailable, and \(3\) strengthening our pre-release validation to confirm that required configuration is in place before a new feature is deployed.

We have deployed a fix after identifying issues accepting events via the Events API in the US. Events are being accepted again, and we are monitoring to ensure stability.

The issue affecting the Events API in the US has been resolved. All systems are now operating normally. The issue means that events sent to the API may not have been recorded for the span of time from 7:34pm to 7:48pm EDT.

We are Investigating Reports of Problems with Ask Scout in the EU Partition

We have mitigated the issue and Ask Scout threads are working in the EU.

This incident has been resolved.