Yext Outage History

Started Oct 27, 2026, 08:29 PM UTC· resolved Oct 27, 2026, 09:54 PM UTC

1. monitoring Oct 27, 2026, 08:29 PM UTC

   We experienced elevated errors affecting Analytics, Search, Pages, Live API, and Streams API services hosted in our EU environment. During this disruption, users may have encountered errors loading pages, retrieving search results, or making API requests. Traffic has been restored to the affected infrastructure, and services are recovering. Our team is monitoring to confirm continued stability. We will provide another update once the incident is fully resolved.

2. resolved Oct 27, 2026, 09:54 PM UTC

   On October 27, 2026, from approximately 4:00 p.m. to 4:20 p.m. EDT (20:00–20:20 UTC), services hosted in our EU environment experienced elevated errors affecting Search, Pages, Live API, Streams API, and Analytics event collection. Users may have encountered errors loading pages, retrieving search results, or making API requests. Some analytics pixel events were not collected during the disruption. Traffic was restored to the affected infrastructure, and subsequent monitoring confirmed stable operation. We apologize for the disruption. We will share a post-incident review with additional details about the cause, impact, and steps we are taking to reduce the risk of recurrence.

3. postmortem Nov 03, 2026, 03:44 PM UTC

   On October 27, 2026, between approximately 19:55 and 20:20 UTC, we experienced elevated errors affecting Search, Pages, Live API, Streams API, and Analytics services hosted in our EU environment. During this period, users may have encountered errors loading pages, retrieving search results, or making API requests. Analytics event collection was also interrupted, resulting in the loss of approximately 22 minutes of analytics pixel events. Most Pages requests continued to be served from our CDN cache. **Cause and resolution** The disruption occurred during maintenance on application servers in our EU infrastructure. The maintenance process did not reconnect servers to the public load balancers in the intended sequence. Maintenance also overlapped across two EU serving locations, interrupting traffic to the affected services. Traffic was restored as the servers reconnected to the load balancers, and services recovered. We continued monitoring to confirm stability before closing the incident at approximately 21:53 UTC. **Prevention** We have merged fixes to the maintenance automation to: * Prevent simultaneous maintenance across the affected EU serving locations. * Ensure servers reconnect to the public load balancers in the intended sequence. We apologize for the disruption and the resulting gaps in analytics reporting.

Read the full incident report →

Started Oct 20, 2026, 08:29 AM UTC· resolved Oct 20, 2026, 09:16 AM UTC

1. resolved Oct 20, 2026, 08:30 AM UTC

   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.

Read the full incident report →

Started Oct 14, 2026, 03:50 PM UTC· resolved Oct 14, 2026, 05:15 PM UTC

1. resolved Oct 14, 2026, 02:50 PM UTC

   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.

Read the full incident report →

Started Sep 09, 2026, 04:10 PM UTC· resolved Sep 10, 2026, 02:13 PM UTC

1. resolved Sep 09, 2026, 04:00 PM UTC

   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.

Read the full incident report →

Started Sep 03, 2026, 04:26 PM UTC· resolved Sep 03, 2026, 05:41 PM UTC

1. identified Sep 03, 2026, 04:26 PM UTC

   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.

2. monitoring Sep 03, 2026, 04:55 PM UTC

   A fix has been deployed to address the inbound voice issue affecting a subset of users.

3. resolved Sep 03, 2026, 05:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2026, 03:09 PM UTC· resolved Sep 02, 2026, 05:44 PM UTC

1. investigating Sep 02, 2026, 03:09 PM UTC

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

2. investigating Sep 02, 2026, 03:21 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 02, 2026, 03:40 PM UTC

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

4. resolved Sep 02, 2026, 05:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 17, 2026, 03:36 PM UTC· resolved Aug 17, 2026, 05:18 PM UTC

1. investigating Aug 17, 2026, 03:36 PM UTC

   We are currently investigating this issue.

2. identified Aug 17, 2026, 03:48 PM UTC

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

3. monitoring Aug 17, 2026, 04:09 PM UTC

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

4. resolved Aug 17, 2026, 05:18 PM UTC

   This incident has been resolved.

5. postmortem Aug 26, 2026, 06:01 PM UTC

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

Read the full incident report →

Started Aug 17, 2026, 02:32 PM UTC· resolved Aug 17, 2026, 09:37 PM UTC

1. identified Aug 17, 2026, 02:32 PM UTC

   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.

2. monitoring Aug 17, 2026, 05:06 PM UTC

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

3. resolved Aug 17, 2026, 09:37 PM UTC

   This incident is resolved.

Read the full incident report →

Started Aug 13, 2026, 08:46 AM UTC· resolved Aug 13, 2026, 01:45 PM UTC

1. investigating Aug 13, 2026, 08:46 AM UTC

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

2. identified Aug 13, 2026, 09:22 AM UTC

   We have identified the issue and are working on remediation.

3. monitoring Aug 13, 2026, 09:29 AM UTC

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

4. resolved Aug 13, 2026, 01:45 PM UTC

   This incident is resolved.

Read the full incident report →

Started Aug 10, 2026, 10:30 AM UTC· resolved Aug 10, 2026, 10:30 AM UTC

1. resolved Aug 10, 2026, 10:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 28, 2026, 09:40 PM UTC· resolved Jul 29, 2026, 09:11 PM UTC

1. identified Jul 28, 2026, 09:40 PM UTC

   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.

2. identified Jul 28, 2026, 09:40 PM UTC

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

3. monitoring Jul 29, 2026, 02:28 PM UTC

   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.

4. resolved Jul 29, 2026, 09:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2026, 06:00 AM UTC· resolved Jul 23, 2026, 06:00 AM UTC

1. resolved Jul 23, 2026, 06:00 AM UTC

   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.

Read the full incident report →

Started Jul 17, 2026, 08:50 AM UTC· resolved Jul 18, 2026, 10:30 AM UTC

1. investigating Jul 17, 2026, 08:50 AM UTC

   File assets are failing to load in customer accounts

2. monitoring Jul 17, 2026, 10:26 AM UTC

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

3. monitoring Jul 17, 2026, 04:51 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jul 18, 2026, 10:30 AM UTC

   This incident is resolved.

5. postmortem Jul 29, 2026, 08:53 PM UTC

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

Read the full incident report →

Started Jul 16, 2026, 11:41 PM UTC· resolved Jul 17, 2026, 12:36 AM UTC

1. identified Jul 16, 2026, 11:41 PM UTC

   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/

2. monitoring Jul 16, 2026, 11:55 PM UTC

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

3. resolved Jul 17, 2026, 12:36 AM UTC

   This incident is resolved.

Read the full incident report →

Started Jul 16, 2026, 06:32 PM UTC· resolved Jul 17, 2026, 02:16 AM UTC

1. investigating Jul 16, 2026, 06:32 PM UTC

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

2. investigating Jul 16, 2026, 09:01 PM UTC

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

3. monitoring Jul 17, 2026, 12:00 AM UTC

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

4. resolved Jul 17, 2026, 02:16 AM UTC

   This incident is resolved.

5. postmortem Jul 29, 2026, 08:45 PM UTC

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

Read the full incident report →

Started Jul 16, 2026, 02:05 PM UTC· resolved Jul 16, 2026, 11:43 PM UTC

1. investigating Jul 16, 2026, 02:05 PM UTC

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

2. monitoring Jul 16, 2026, 02:40 PM UTC

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

3. identified Jul 16, 2026, 03:56 PM UTC

   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.

4. identified Jul 16, 2026, 05:01 PM UTC

   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.

5. resolved Jul 16, 2026, 11:43 PM UTC

   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.

Read the full incident report →

Started Jul 16, 2026, 01:08 PM UTC· resolved Jul 16, 2026, 03:05 PM UTC

1. investigating Jul 16, 2026, 01:08 PM UTC

   We are investigating reports of errors in Hearsay Platform.

2. identified Jul 16, 2026, 01:10 PM UTC

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

3. identified Jul 16, 2026, 01:52 PM UTC

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

4. monitoring Jul 16, 2026, 02:04 PM UTC

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

5. resolved Jul 16, 2026, 03:05 PM UTC

   This incident has been resolved.

6. postmortem Jul 21, 2026, 07:12 PM UTC

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

Read the full incident report →

Started Jul 15, 2026, 02:48 PM UTC· resolved Jul 15, 2026, 08:07 PM UTC

1. identified Jul 15, 2026, 02:48 PM UTC

   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.

2. identified Jul 15, 2026, 05:43 PM UTC

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

3. resolved Jul 15, 2026, 08:07 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 14, 2026, 09:45 AM UTC· resolved Jul 14, 2026, 11:30 AM UTC

1. investigating Jul 14, 2026, 09:45 AM UTC

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

2. identified Jul 14, 2026, 10:13 AM UTC

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

3. monitoring Jul 14, 2026, 10:35 AM UTC

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

4. resolved Jul 14, 2026, 11:30 AM UTC

   This incident has been resolved.

5. postmortem Jul 17, 2026, 09:00 AM UTC

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

Read the full incident report →

Started Jul 14, 2026, 12:23 AM UTC· resolved Jul 14, 2026, 12:46 AM UTC

1. monitoring Jul 14, 2026, 12:23 AM UTC

   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.

2. resolved Jul 14, 2026, 12:46 AM UTC

   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.

Read the full incident report →

Started Jul 03, 2026, 01:40 PM UTC· resolved Jul 04, 2026, 02:11 PM UTC

1. investigating Jul 03, 2026, 01:40 PM UTC

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

2. monitoring Jul 03, 2026, 02:25 PM UTC

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

3. resolved Jul 04, 2026, 02:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 02, 2026, 05:28 AM UTC· resolved Jul 02, 2026, 05:39 AM UTC

1. investigating Jul 02, 2026, 05:28 AM UTC

   We are currently investigating an issue affecting portions of the Hearsay web application. Some users may experience intermittent failures when navigating or interacting with certain areas of the web interface. The impact is limited to the web UI. Mobile applications, Salesforce integrations, and all backend data processing continue to operate normally.

2. identified Jul 02, 2026, 05:33 AM UTC

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

3. resolved Jul 02, 2026, 05:39 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2026, 04:00 AM UTC· resolved Jun 30, 2026, 04:00 AM UTC

1. resolved Jun 30, 2026, 04:00 AM UTC

   Semantic search functionality in Yext Search had elevated error rates in our EU regions from 6/29/2026 from 12 AM to 4 AM. Semantic search functionality has since been resolved.

Read the full incident report →

Started Jun 29, 2026, 05:00 PM UTC· resolved Jun 29, 2026, 07:16 PM UTC

1. monitoring Jun 29, 2026, 05:00 PM UTC

   We identified elevated error rates in our Analytics systems, affecting the Analytics tab in the customer portal, some Scout functionality, and other Analytics-related functionality across the customer portal. We have implemented a fix, and Analytics requests are currently being served as normal. We are continuing to monitor to ensure stability.

2. resolved Jun 29, 2026, 07:16 PM UTC

   This incident is resolved.

Read the full incident report →

Started Jun 22, 2026, 09:23 PM UTC· resolved Jun 23, 2026, 09:04 AM UTC

1. resolved Jun 22, 2026, 09:30 PM UTC

   In the EU production environment, the Analytics section of the customer portal and the Analytics API experienced elevated error rates from 2026/06/22 9:23 PM UTC until 2026/06/23 9:04 AM UTC. Our engineering team has implemented a fix, and has added additional safeguards to prevent recurrence of similar issues in the future.

Read the full incident report →