Major incident

Yext: Image Serving Partially Degraded

Affected: Pages Serving, Search Serving

Current status of Yext: Operational — live Yext status

Timeline

1. Jul 16, 2026, 18:32 UTC
   investigating
   A subset of images are failing to load on our customer's Pages and Search responses.
2. Jul 16, 2026, 21:01 UTC
   investigating
   We are still investigating the image loading failures and are working with our CDN provider to assess the issue
3. Jul 17, 2026, 00:00 UTC
   monitoring
   We have remediated the errors. We will continue to monitor the situation.
4. Jul 17, 2026, 02:16 UTC
   resolved
   This incident is resolved.
5. Jul 29, 2026, 20:45 UTC
   postmortem
   # **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.

Updates as published by Yext (original).