Yext Outage History

Started Feb 02, 2026, 07:39 PM UTC· resolved Feb 03, 2026, 03:09 PM UTC

1. investigating Feb 02, 2026, 07:39 PM UTC

   We are investigating reports of delayed ingestion of Analytics Events affecting Pages and Search analytics queries starting from 2026/01/29. Some users may observed reduced analytics data for the affected time period. Our team is actively working to identify the root cause.

2. identified Feb 02, 2026, 07:55 PM UTC

   We have identified the problem and are working on deploying a mitigation.

3. monitoring Feb 02, 2026, 08:59 PM UTC

   We have deployed a fix and analytics ingestion has restarted, we are monitoring the system for regression and ensuring the system catches up.

4. resolved Feb 03, 2026, 03:09 PM UTC

   The issue affecting Analytics Event ingestion has been resolved. All systems are now operating normally. Events ingested from 2026-01-30 UTC through 2026-02-02 UTC were affected, and metric queries made between 2026-01-30 00:00:00 UTC and 2026-02-03 01:45:00 UTC may have showed reduced data for the affected timeframe. All data for the affected timeframe has been restored and should now be reflected in metric queries. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jan 22, 2026, 11:00 PM UTC· resolved Jan 22, 2026, 11:00 PM UTC

1. resolved Jan 29, 2026, 03:23 PM UTC

   From approximately January 22, 2027 at 6 PM EST to January 23, 2027 at 7 PM EST, a subset of scheduled exports failed to send due to an internal issue. The issue has been resolved. Missed exports will not be re-sent and will instead run at the next scheduled cadence. No action is required.

Read the full incident report →

Started Jan 21, 2026, 07:12 PM UTC· resolved Jan 22, 2026, 01:13 AM UTC

1. investigating Jan 21, 2026, 07:12 PM UTC

   We are investigating reports for Missing Google Analytics data for early 2024

2. identified Jan 21, 2026, 08:30 PM UTC

   We have identified the problem and are working on a fix

3. resolved Jan 22, 2026, 01:13 AM UTC

   We have resolved the issue and restored the missing analytics data

Read the full incident report →

Started Jan 13, 2026, 07:44 PM UTC· resolved Jan 13, 2026, 07:44 PM UTC

1. resolved Jan 13, 2026, 07:44 PM UTC

   Scout has had an ongoing issue with website data since ~ 12/12/25 which we have been working to resolve. As of 1/13/25 at 11:35 am EST we have addressed the underlying issues and purged the bad data from our system. We are currently working on re-scanning all impacted accounts with an estimated time of completion of close of business on January 14.

Read the full incident report →

Started Jan 06, 2026, 11:30 PM UTC· resolved Jan 06, 2026, 11:30 PM UTC

1. resolved Jan 22, 2026, 10:43 PM UTC

   From January 6th, 2026 at 5:22 PM EST until January 21st, 2026 at 6:30 PM EST, some number of listings experienced errors that prevented them from going live on publishers. These errors occurred because the Listings system was out of sync with current information in the Knowledge Graph, causing invalid "not synced" errors to be shown, and some listings to be permanently stuck in a processing state. The underlying problem has been resolved, and as of last night, all Listings affected by this should be working as expected.

Read the full incident report →

Started Dec 24, 2025, 06:01 PM UTC· resolved Dec 24, 2025, 07:39 PM UTC

1. investigating Dec 24, 2025, 06:01 PM UTC

   We are investigating reports of errors in the user portal.

2. identified Dec 24, 2025, 06:23 PM UTC

   We have identified the issue and are working on remediation.

3. identified Dec 24, 2025, 06:59 PM UTC

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

4. identified Dec 24, 2025, 07:19 PM UTC

   The fix has been deployed to the production.

5. monitoring Dec 24, 2025, 07:22 PM UTC

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

6. resolved Dec 24, 2025, 07:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 18, 2025, 06:15 PM UTC· resolved Dec 19, 2025, 01:10 AM UTC

1. investigating Dec 18, 2025, 06:15 PM UTC

   We are investigating reports of login errors on the Yext Platform.

2. monitoring Dec 18, 2025, 06:27 PM UTC

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

3. resolved Dec 19, 2025, 01:10 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 18, 2025, 12:49 AM UTC· resolved Dec 18, 2025, 01:33 AM UTC

1. investigating Dec 18, 2025, 12:49 AM UTC

   We are currently investigating reports of errors when attempting to access the Hearsay website.

2. monitoring Dec 18, 2025, 01:01 AM UTC

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

3. resolved Dec 18, 2025, 01:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 17, 2025, 02:44 PM UTC· resolved Dec 17, 2025, 05:31 PM UTC

1. investigating Dec 17, 2025, 02:44 PM UTC

   We are investigating reports of errors when responding to Reviews or leaving new First Party Reviews. Despite these errors, responses and reviews are being successfully processed.

2. monitoring Dec 17, 2025, 04:12 PM UTC

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

3. resolved Dec 17, 2025, 05:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 15, 2025, 06:29 PM UTC· resolved Dec 16, 2025, 08:13 AM UTC

1. investigating Dec 15, 2025, 06:29 PM UTC

   We are investigating reports of delays in Listings Updates for the Facebook platform.

2. identified Dec 15, 2025, 07:05 PM UTC

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

3. monitoring Dec 15, 2025, 08:06 PM UTC

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

4. resolved Dec 16, 2025, 08:13 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 08, 2025, 05:19 PM UTC· resolved Dec 13, 2025, 12:34 PM UTC

1. investigating Dec 08, 2025, 05:19 PM UTC

   We are investigating reports of inaccurate data in some customer accounts with scans run on or after December 3rd.

2. investigating Dec 08, 2025, 11:11 PM UTC

   We are continuing to investigate the issue.

3. identified Dec 09, 2025, 04:24 PM UTC

   We have deployed a mitigation that has re-enabled accurate data in our real time scan api. We have are testing mitigations for bulk customer scans and will purge the bad data from customer accounts once we have a mitigation in place.

4. identified Dec 10, 2025, 08:42 PM UTC

   We are continuing to work through mitigations to return to normal scanning operations. As of this morning all bad scans between 12/3 and 12 PM EST 12/10 have been purged from the system. Once we are able to fully mitigate the issue, we will re-scan all impacted customers.

5. monitoring Dec 12, 2025, 07:36 PM UTC

   Our mitigation efforts have succeeded in allowing scans to get correct data and we are no in progress re-processing all accounts that had scanning delayed due to the incident. We will provide another update once all accounts have gotten into a good state.

6. resolved Dec 13, 2025, 12:34 PM UTC

   All impacted customers have been re-scanned and scanning operations have returned to normal.

Read the full incident report →

Started Dec 05, 2025, 09:08 AM UTC· resolved Dec 05, 2025, 09:43 AM UTC

1. identified Dec 05, 2025, 09:08 AM UTC

   We are experiencing widespread outages in our APIs and Customer Portal due to an ongoing incident with our CDN provider, Cloudflare. https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q

2. monitoring Dec 05, 2025, 09:19 AM UTC

   Cloudflare is reporting that the issue has been mitigated. Yext APIs and the customer platform have been restored to normal functionality. We will continue to monitor the situation.

3. resolved Dec 05, 2025, 09:43 AM UTC

   Cloudflare is reporting that the incident is resolved, and all Yext systems have been restored to normal functionality.

Read the full incident report →

Started Nov 24, 2025, 10:11 PM UTC· resolved Nov 24, 2025, 10:14 PM UTC

1. investigating Nov 24, 2025, 10:11 PM UTC

   Some Generative Answers requests are failing.

2. monitoring Nov 24, 2025, 10:12 PM UTC

   An update to Yext Search's Generative Answers caused some generative answer requests to fail to return starting at 1:13 PM EST. We identified the issue and resolved it at 4:38 PM EST.

3. resolved Nov 24, 2025, 10:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 19, 2025, 05:09 PM UTC· resolved Nov 19, 2025, 05:59 PM UTC

1. investigating Nov 19, 2025, 05:09 PM UTC

   We are investigating errors adding images and other files to the Knowledge Graph, both via the Customer Portal and via the API.

2. monitoring Nov 19, 2025, 05:19 PM UTC

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

3. resolved Nov 19, 2025, 05:59 PM UTC

   This incident is resolved.

Read the full incident report →

Started Nov 19, 2025, 04:07 PM UTC· resolved Nov 19, 2025, 04:58 PM UTC

1. investigating Nov 19, 2025, 04:07 PM UTC

   We are currently investigating this issue.

2. investigating Nov 19, 2025, 04:41 PM UTC

   We are continuing to investigate this issue.

3. resolved Nov 19, 2025, 04:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 02:16 PM UTC· resolved Nov 18, 2025, 05:31 PM UTC

1. identified Nov 18, 2025, 02:16 PM UTC

   The issue has been identified and the CDN provider is working on a fix. More information can be found on their status site: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

2. monitoring Nov 18, 2025, 04:24 PM UTC

   Cloudflare believes they have remediated the issue. We will continue to monitor the situation.

3. resolved Nov 18, 2025, 05:31 PM UTC

   This incident is resolved.

Read the full incident report →

Started Nov 17, 2025, 02:47 PM UTC· resolved Nov 17, 2025, 05:04 PM UTC

1. investigating Nov 17, 2025, 02:47 PM UTC

   We are investigating errors in our Public API and have taken it down temporarily for maintenance.

2. investigating Nov 17, 2025, 03:07 PM UTC

   Sites and Actions are also currently impacted as a result of the API issues.

3. identified Nov 17, 2025, 03:20 PM UTC

   We have identified the issue and are working to correct it.

4. monitoring Nov 17, 2025, 03:36 PM UTC

   We have resolved the errors and re-enabled the API. We will continue to monitor for lingering impact.

5. resolved Nov 17, 2025, 05:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 14, 2025, 04:34 PM UTC· resolved Nov 14, 2025, 09:01 PM UTC

1. investigating Nov 14, 2025, 04:34 PM UTC

   We are investigating a connection issue between our Search serving systems and our more advanced search models. This connection issue is leading to a degradation in search result accuracy (results are being returned in a less than optimal order, but are still returning). Search indexing is also delayed as a result of this issue.

2. identified Nov 14, 2025, 05:19 PM UTC

   We have identified the issue and are working on a fix.

3. monitoring Nov 14, 2025, 06:32 PM UTC

   We have deployed a fix and are monitoring for regression

4. resolved Nov 14, 2025, 09:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 05, 2025, 07:47 PM UTC· resolved Nov 06, 2025, 01:53 AM UTC

1. investigating Nov 05, 2025, 07:47 PM UTC

   We are looking into an issue with the Google User Photos metric.

2. identified Nov 05, 2025, 09:11 PM UTC

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

3. monitoring Nov 06, 2025, 01:04 AM UTC

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

4. resolved Nov 06, 2025, 01:53 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 31, 2025, 03:50 AM UTC· resolved Oct 31, 2025, 04:35 PM UTC

1. investigating Oct 31, 2025, 03:50 AM UTC

   We are currently investigating this issue.

2. investigating Oct 31, 2025, 04:09 AM UTC

   The issue has been identified and a fix is being implemented. The issue only impacts new or updated Knowledge Graph locations and entities since issues started occurring, pre-existing data continues to operate as expected.

3. identified Oct 31, 2025, 04:34 AM UTC

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

4. monitoring Oct 31, 2025, 04:36 AM UTC

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

5. resolved Oct 31, 2025, 04:35 PM UTC

   We've finished processing the delayed data and systems look healthy. This incident has been resolved.

Read the full incident report →

Started Oct 30, 2025, 05:43 PM UTC· resolved Oct 31, 2025, 01:31 AM UTC

1. identified Oct 30, 2025, 05:43 PM UTC

   The issue has been identified and a fix is being implemented. The issue only impacts new or updated Knowledge Graph locations and entities since 12pm EST, pre-existing data continues to operate as expected.

2. monitoring Oct 30, 2025, 07:29 PM UTC

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

3. resolved Oct 31, 2025, 01:31 AM UTC

   The delayed data has been processed and this system continues to be operational, so the incident has been resolved.

Read the full incident report →

Started Oct 21, 2025, 05:59 PM UTC· resolved Oct 22, 2025, 01:08 AM UTC

1. investigating Oct 21, 2025, 05:59 PM UTC

   We are investigating reports of increased error rates in Search.

2. monitoring Oct 21, 2025, 09:11 PM UTC

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

3. resolved Oct 22, 2025, 01:08 AM UTC

   This incident is resolved.

Read the full incident report →

Started Oct 21, 2025, 01:23 PM UTC· resolved Oct 21, 2025, 06:19 PM UTC

1. investigating Oct 21, 2025, 01:23 PM UTC

   We are currently investigating this issue.

2. investigating Oct 21, 2025, 01:46 PM UTC

   We are continuing to investigate this issue.

3. identified Oct 21, 2025, 02:44 PM UTC

   We have identified the issue and are working on remediation.

4. monitoring Oct 21, 2025, 04:03 PM UTC

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

5. resolved Oct 21, 2025, 06:19 PM UTC

   This incident is resolved.

Read the full incident report →

Started Oct 20, 2025, 03:05 PM UTC· resolved Oct 20, 2025, 06:28 PM UTC

1. investigating Oct 20, 2025, 03:05 PM UTC

   We are currently experiencing delays in processing Expert Services ETLs.

2. monitoring Oct 20, 2025, 03:46 PM UTC

   Our ETL system has recovered, the issues were related to the ongoing Amazon Web Services incident. We are monitoring progress on running ETLs.

3. resolved Oct 20, 2025, 06:28 PM UTC

   All ETLs are behaving normally

Read the full incident report →

Started Oct 20, 2025, 01:42 PM UTC· resolved Oct 20, 2025, 10:30 PM UTC

1. investigating Oct 20, 2025, 01:42 PM UTC

   We are investigating reports of elevated error rates in the Scout Real Time Scan API.

2. identified Oct 20, 2025, 01:48 PM UTC

   The ongoing Snowflake Incident is causing impacts on the Yext Analytics platform and systems that rely upon it, such as the Scout Interactive API. https://status.snowflake.com/incidents/gvmvnx7lyxjj We are monitoring Snowflake's ongoing incident and will provide updates as we can.

3. monitoring Oct 20, 2025, 02:56 PM UTC

   Our automated monitoring checks have recovered. We are continuing to monitor Snowflake's status for updates. Some analytics queries may still be slower than usual.

4. monitoring Oct 20, 2025, 06:29 PM UTC

   We are continuing to monitor system performance as a result of the ongoing incident with Snowflake

5. resolved Oct 20, 2025, 10:30 PM UTC

   This incident is resolved.

Read the full incident report →