Yext Incident History

This incident has been resolved.

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.

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

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.

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

This incident is resolved.

We are continuing to monitor for any further issues.

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

File assets are failing to load in customer accounts

# **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.

This incident is resolved.

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

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

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

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.

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

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.

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.

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.

# **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.

This incident has been resolved.

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

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

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

We are investigating reports of errors in Hearsay Platform.

This incident has been resolved.

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

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

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

We are investigating reports of errors in Hearsay Platform.

This incident is resolved.

We are continuing to monitor for any further issues.

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

File assets are failing to load in customer accounts

# **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.

This incident has been resolved.

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

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

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

This incident is resolved.

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

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

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

This incident is resolved.

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

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/

This incident is resolved.

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

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 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.

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 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.

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

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

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.

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 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.

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

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