Loading
Applying language and content...
Loading status page
Checking service and reports...
51 Yext incidents · 2025년 11월 — official updates, affected components, duration and resolution details.
우리는 미국 이벤트 API를 통해 이벤트를 수락 한 후 수정을 배포했습니다. 사건은 다시 받아들여지고, 우리는 안정성을 지키는 감시입니다.
미국의 이벤트 API에 영향을 미치는 문제는 해결되었습니다. 모든 시스템은 현재 작동 중입니다. 이 문제는 API에 전송 된 이벤트가 7 : 34pm에서 7 : 48pm EDT의 스팬에 기록되지 않을 수 있음을 의미합니다.
공식 인시던트 업데이트를 자동 번역했습니다.
우리는 EU 파티션에서 Ask Scout와 문제의 조사 보고서입니다
우리는 문제가 mitigated 및 Ask Scout 스레드는 EU에서 일하고 있습니다.
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
우리는 현재 Hearsay 웹 응용 프로그램의 일부에 영향을 미치는 문제를 조사하고 있습니다. 일부 사용자는 웹 인터페이스의 특정 영역과 상호작용 실패를 경험할 수 있습니다. 영향은 웹 UI로 제한됩니다. 모바일 애플리케이션, Salesforce 통합 및 모든 백엔드 데이터 처리는 일반적으로 작동하도록 계속됩니다.
문제는 식별되고 수정이 구현됩니다.
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
Yext Search의 Semantic 검색 기능은 12 AM에서 4 AM까지 6 / 29 / 2026에서 EU 지역의 오류율을 높였습니다. Semantic 검색 기능은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
우리는 우리의 분석 시스템에서 높은 오류율을 확인, 고객 포털의 분석 탭에 영향을, 일부 스카우트 기능, 그리고 고객 포털의 다른 분석 관련 기능. 우리는 수정을 구현하고, Analytics 요청은 현재 정상으로 제공됩니다. 우리는 안정성을 보장하기 위해 계속됩니다.
이 사건은 해결됩니다.
공식 인시던트 업데이트를 자동 번역했습니다.
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.
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.
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.
We have identified and remediated the issue. We confirmed there was no impact to customers. This incident is resolved.
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.
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.
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.
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.
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.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
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.
# **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.
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.
LinkedIn has implemented a fix and we are monitoring results.
This incident has been resolved.
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
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified errors in the Listings pages within the portal. We have remediated the errors and will continue to monitor the situation.
This incident has been resolved.
We have identified an issue that has been causing delays in Crawler runs since 4:00 AM EST earlier today (May 12, 2026).
Crawler runs are still delayed; we are continuing to work on figuring out the source of the delays.
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.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the impacted systems.
This incident has been resolved.
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.
We are currently investigating reports of publishing delays for a subset of Pages sites.
The issue has been identified and a fix is being implemented.
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.
This incident has been resolved.
We are investigating reports of a partial outage in Analytics API
The issue has been identified and a fix is being implemented.
We have mitigated the issue for most affected customers. We are continuing to work on completely resolving the issue.
We have remediated the issue. We will continue to monitor the situation.
This incident is resolved.