Istoricul incidentelor Yext

1. 14 iulie 2026 la 00:23 UTCmonitoring

   Am implementat un fix după identificarea problemelor care acceptă evenimente prin intermediul API Evenimente în SUA. Evenimentele sunt acceptate din nou şi monitorizăm pentru a asigura stabilitatea.

2. 14 iulie 2026 la 00:46 UTCresolved

   Problema care afectează API Evenimente în SUA a fost rezolvată. Toate sistemele funcţionează normal. Problema înseamnă că evenimentele trimise către API nu au fost înregistrate pentru intervalul de timp de la 7:34pm la 7:48pm EDT.

Traducere automată din actualizarea oficială a incidentului.

1. 3 iulie 2026 la 13:40 UTCinvestigating

   Investigăm rapoarte privind problemele cu Cercetașii în cadrul Partiției UE

2. 3 iulie 2026 la 14:25 UTCmonitoring

   Am redus problema și în UE funcționează fire de Cercetaș.

3. 4 iulie 2026 la 14:11 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 2 iulie 2026 la 05:28 UTCinvestigating

   Investigăm în prezent o problemă care afectează porțiuni ale aplicației web Hearsay. Unii utilizatori pot experimenta eșecuri intermitente atunci când navighează sau interacționează cu anumite zone ale interfeței web. Impactul este limitat la UI web. Aplicaţiile mobile, integrarea forţelor de vânzare şi procesarea datelor pe suport continuă să funcţioneze normal.

2. 2 iulie 2026 la 05:33 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 2 iulie 2026 la 05:39 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iunie 2026 la 16:14 UTCresolved

   Funcţionalitatea de căutare semantică în Yext Search a avut rate ridicate de eroare în regiunile noastre UE de la 6/29/2026 la 12 AM la 4 AM. Funcţionalitatea de căutare semantică a fost de atunci rezolvată.

Traducere automată din actualizarea oficială a incidentului.

1. 29 iunie 2026 la 17:00 UTCmonitoring

   Am identificat rate de eroare ridicate în sistemele noastre Analytics, care afectează fila Analytics în portalul client, unele funcționalitate Scout, și alte funcționalitate legate de Analytics pe portalul client. Am implementat un fix, iar cererile de analiză sunt în prezent servite ca normale. Continuăm să monitorizăm pentru a asigura stabilitatea.

2. 29 iunie 2026 la 19:16 UTCresolved

   Acest incident este rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iunie 2026 la 19:07 UTCresolved

   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.

1. 11 iunie 2026 la 11:32 UTCresolved

   We found an issue that caused our "Connect to Google/Yelp/Facebook" Optimization API tasks to not be returned from May 12, 2026 ~3:00 PM EST to June 11, 2026 7:30 AM EST. We have resolved the issue, and expect these tasks should be properly returned in the API for all customers now.

1. 4 iunie 2026 la 20:16 UTCinvestigating

   We are aware of an issue affecting the content library that is causing errors for some users. We are investigating and will provide an update shortly.

2. 4 iunie 2026 la 20:30 UTCresolved

   We have identified and remediated the issue. We confirmed there was no impact to customers. This incident is resolved.

1. 3 iunie 2026 la 20:15 UTCinvestigating

   We are investigating reports of reports asynchronously generated via the Analytics API being inaccessible. Our team is actively working to identify the root cause. We will update this page when we have further information.

2. 3 iunie 2026 la 20:52 UTCmonitoring

   We have remediated the issue, and all new reports requested via the Analytics API should now be accessible. Clients who are encountering errors with loading previously-generated reports should make a new request to the Analytics API to regenerate their desired reports. We will continue to monitor the situation.

3. 3 iunie 2026 la 22:38 UTCresolved

   The issue affecting Analytics API has been resolved. As previously noted, all new reports requested via the Analytics API should now be accessible. Clients who are encountering errors with loading previously-generated reports should make a new request to the Analytics API to regenerate their desired reports.

1. 3 iunie 2026 la 08:52 UTCinvestigating

   We are currently experiencing degraded performance affecting parts of the Reviews Portal. Some users may encounter increased latency and intermittent errors when accessing certain functionality. Our team is actively investigating and working to mitigate the issue. We will provide additional updates as more information becomes available. Impact: Reviews Portal performance may be degraded, including intermittent errors and slower response times.

2. 3 iunie 2026 la 09:43 UTCmonitoring

   We have identified and mitigated the issue that was causing degraded performance in the Reviews Portal and related functionality. System load has returned to normal levels, and service performance has stabilized. We are continuing to monitor the platform closely to ensure the recovery is sustained. Users should no longer experience the elevated latency, timeouts, or intermittent errors reported earlier.

3. 3 iunie 2026 la 11:03 UTCresolved

   This incident has been resolved.

1. 2 iunie 2026 la 17:32 UTCinvestigating

   We have identified an issue where a subset of Managed Services ETLs that rely on SFTP file drops failed. We are working on identifying the impacted jobs and time frame.

2. 2 iunie 2026 la 18:09 UTCidentified

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

3. 3 iunie 2026 la 18:10 UTCresolved

   We have completed our impact assessment and are following up directly with any affected clients. We will continue to monitor closely to ensure normal processing is maintained.

4. 12 iunie 2026 la 19:36 UTCpostmortem

   # **Summary** From approximately 6:45PM ET on Sunday, June 1, 2026, until 2:06PM ET on Monday, June 2, 2026, a subset of customers using Yext Managed Services ETL workflows experienced processing failures related to a Yext-managed file ingestion service. During this period, a capacity constraint within a Yext-managed file ingestion service prevented some incoming files from being fully processed, causing downstream ETL processing failures. For a small number of customers, incomplete data resulted in incorrect business hours being published to listing publishers. Subsequent successful ETL runs restored the correct information, and verification completed on June 3 confirmed normal processing had resumed for all affected customers. # **Root Cause** The issue occurred when a capacity constraint developed within infrastructure supporting Managed Services file ingestion workflows. As available capacity was exhausted, some incoming files could not be fully written and were stored as incomplete files. These files were subsequently processed by downstream ETL workflows, resulting in processing failures and data errors issues for a subset of customers. The issue was not detected immediately because the failure condition was not surfaced by the automated checks and alerts in place at the time. Consequently, the issue was identified after customer impact had begun. We have identified this monitoring gap and are implementing additional monitoring and alerting to improve detection and response times for similar issues. # **Remediation** After identifying the issue, the team restored capacity on the affected service, returning file ingestion and processing to normal operation at 2:06PM ET on June 2. We have identified and are implementing several follow-up actions to prevent similar incidents in the future, including: * Adding additional monitoring and alerting for critical Managed Services file ingestion infrastructure. * Implementing automated capacity management and retention controls to reduce the risk of resource exhaustion. * Improving validation of incoming files so incomplete files are detected and rejected before downstream processing.

1. 20 mai 2026 la 12:17 UTCinvestigating

   We are currently investigating elevated error rates from LinkedIn APIs used by Hearsay Social to monitor LinkedIn user activity, including posts, comments, and profile updates. Customers may experience delays in LinkedIn activity capture and monitoring. We are working with LinkedIn and monitoring recovery. We will provide another update as more information becomes available.

2. 20 mai 2026 la 15:56 UTCmonitoring

   LinkedIn has implemented a fix and we are monitoring results.

3. 20 mai 2026 la 16:37 UTCresolved

   This incident has been resolved.

1. 19 mai 2026 la 15:07 UTCinvestigating

   We are seeing degraded performance with some areas of the Hearsay application likely due to heavy traffic. We are actively investigating and will update shortly. No data loss is expected at this time

2. 19 mai 2026 la 15:59 UTCidentified

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

3. 19 mai 2026 la 16:02 UTCmonitoring

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

4. 19 mai 2026 la 16:19 UTCresolved

   This incident has been resolved.

1. 15 mai 2026 la 13:44 UTCinvestigating

   We are seeing degraded performance with some areas of the Hearsay application likely due to heavy traffic. We are actively investigating and will update shortly. No data loss is expected at this time

2. 15 mai 2026 la 14:07 UTCidentified

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

3. 15 mai 2026 la 14:24 UTCmonitoring

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

4. 15 mai 2026 la 15:41 UTCresolved

   This incident has been resolved.

1. 13 mai 2026 la 17:24 UTCmonitoring

   We have identified errors in the Listings pages within the portal. We have remediated the errors and will continue to monitor the situation.

2. 13 mai 2026 la 20:40 UTCresolved

   This incident has been resolved.

1. 12 mai 2026 la 22:33 UTCidentified

   We have identified an issue that has been causing delays in Crawler runs since 4:00 AM EST earlier today (May 12, 2026).

2. 13 mai 2026 la 06:37 UTCidentified

   Crawler runs are still delayed; we are continuing to work on figuring out the source of the delays.

3. 13 mai 2026 la 18:10 UTCmonitoring

   We have resolved the delays causing Crawler runs to be stuck over the last ~34 hours. As part of our resolution, we needed to cancel all active crawls. For customers with one-off or weekly crawl configurations, we have restarted all your crawls (and all but five weekly crawls are still in progress). For customers with daily crawl configurations, you should feel free to manually restart your crawls, or expect that they will run again at their normally scheduled time in the next 24 hours.

4. 13 mai 2026 la 23:45 UTCresolved

   This incident has been resolved.

1. 12 mai 2026 la 16:09 UTCinvestigating

   Due to some underlying infrastructure issues we are working to resolve, data updates in Yext Search may be delayed and Review Language classification is down in Yext Reviews.

2. 12 mai 2026 la 18:57 UTCidentified

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

3. 12 mai 2026 la 19:05 UTCidentified

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

4. 12 mai 2026 la 20:32 UTCmonitoring

   A fix has been implemented and we are monitoring the impacted systems.

5. 13 mai 2026 la 16:34 UTCresolved

   This incident has been resolved.

1. 30 aprilie 2026 la 23:39 UTCresolved

   An issue with the US Customer Portal was identified and mitigated. Between 5:30pm and 6:10pm ET on 4/30/2026, the portal may have been unavailable or the navigation bar may have failed to render. The portal is now operating normally.

1. 29 aprilie 2026 la 13:34 UTCinvestigating

   We are currently investigating reports of publishing delays for a subset of Pages sites.

2. 29 aprilie 2026 la 14:19 UTCidentified

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

3. 29 aprilie 2026 la 17:10 UTCmonitoring

   We have implemented a fix for this issue and publishing has resumed. There was also a partial impact to the Content Portal which has also been mitigated. We will continue to monitor the situation.

4. 30 aprilie 2026 la 13:30 UTCresolved

   This incident has been resolved.

1. 22 aprilie 2026 la 09:54 UTCinvestigating

   We are investigating reports of a partial outage in Analytics API

2. 22 aprilie 2026 la 10:33 UTCidentified

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

3. 22 aprilie 2026 la 11:34 UTCidentified

   We have mitigated the issue for most affected customers. We are continuing to work on completely resolving the issue.

4. 22 aprilie 2026 la 12:17 UTCmonitoring

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

5. 22 aprilie 2026 la 13:29 UTCresolved

   This incident is resolved.