Coveo Cloud 장애 기록

1. 2026년 8월 26일 PM 7:12 UTCinvestigating

   우리는 현재 모든 지역에서 호스팅 빌더를 사용하여 검색 페이지로 영향을 미치는 문제를 조사하고 있습니다. 이 페이지는 현재 사용할 수 없습니다. 우리의 팀은 조사하고 해결될 때까지 일정한 갱신을 포스트할 것입니다.

2. 2026년 8월 26일 PM 7:25 UTCmonitoring

   수정이 시행되고 모든 Hosted 검색 페이지는 현재 운영 중입니다. 우리는 상황을 밀접하게 감시하기 위하여 계속할 것입니다.

3. 2026년 8월 26일 PM 8:17 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 18일 PM 4:34 UTCidentified

   우리는 미국 지역에서 Group Invites에 영향을 미치는 문제를 발견했습니다. 고객은 새로운 사용자를 조직에 초대할 수 없습니다. 우리의 팀은 이미 충격을 투약하고 해결될 때까지 일정한 갱신을 포스트할 것입니다. 당신이 도움이 필요하거나 우리와 접촉에 도착하려면, 우리의 도움말 포털을 방문하시기 바랍니다

2. 2026년 8월 18일 PM 4:52 UTCmonitoring

   이 문제는 해결되었습니다. 감사합니다.

3. 2026년 8월 18일 PM 5:10 UTCresolved

   이 서비스는 마지막 업데이트 이후 완전히 운영됩니다. 이 사건은 해결됩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 4일 PM 8:16 UTCinvestigating

   We're investigating an issue with a service provider affecting Generative Answering in the US region. You may see short-lived spikes in errors when fetching answers from CRGA or Agentic queries. Our team is investigating and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 8월 4일 PM 9:30 UTCmonitoring

   The issue occurring with Generative Answering for some of our US customers has been fixed and we are closely monitoring the service. If you need help or to get in touch with us, please visit our Help Portal

3. 2026년 8월 5일 AM 12:48 UTCresolved

   Between 2:30 PM ET and 4:30 PM ET, a temporary degradation on one of our service providers occurred which caused intermittent errors when interacting with Generative Answering in the US during that time window. The issue has been resolved. If you need help or to get in touch with us, please visit our Help Portal

1. 2026년 7월 17일 PM 12:05 UTCinvestigating

   상업 검색에 영향을 미치는 문제점을 조사하고 있습니다. 고객의 하위 세트를 위해 이전에 존재하는 일부 필드는 상업 API 응답의 추가 Fields에서 누락 될 수 있습니다. 우리의 팀은 조사하고 해결될 때까지 일정한 갱신을 포스트할 것입니다. 당신이 도움이 필요하거나 우리와 접촉에 도착하려면, 우리의 도움말 포털을 방문하시기 바랍니다

2. 2026년 7월 17일 PM 12:26 UTCidentified

   뿌리 원인은 확인되었으며 우리 팀은 문제를 완화하기 위해 노력하고 있습니다.

3. 2026년 7월 17일 PM 12:48 UTCidentified

   우리는 수정을 확인하고 1 시간 이내에 미량화 될 문제를 기대하고있다. 추가 필드 객체에 존재하는 표준 필드에 의존하는 고객은 영향을받습니다. 이 문제는 표준 필드에 직접 의존하여 수행 할 수 있지만 추가 필드를 통해 그들을 사용하는 것보다

4. 2026년 7월 17일 PM 1:16 UTCmonitoring

   수정이 실행되고 작업에 확인되어 충격을 제거했습니다. 우리는 계속 서비스를 모니터링.

5. 2026년 7월 17일 PM 1:55 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 16일 AM 10:56 UTCidentified

   우리는 분석보고에 영향을 미치는 문제와 미국 지역에서 ML 모델의 하위 세트를 확인했습니다. 이 데이터 공유 및 플랫폼보고에 대한 업데이트 방지입니다. 관찰된 데이터는 지연될 수 있습니다. 우리의 팀은 이미 충격을 투약하고 해결될 때까지 일정한 갱신을 포스트할 것입니다. 당신이 도움이 필요하거나 우리와 접촉에 도착하려면, 우리의 도움말 포털을 방문하시기 바랍니다

2. 2026년 7월 16일 PM 4:07 UTCidentified

   우리는 뿌리 원인을 확인하고 우리 팀은 여전히 문제가 해결하기 위해 적극적으로 노력하고 있습니다.

3. 2026년 7월 17일 AM 1:15 UTCidentified

   우리의 팀은 대부분의 경우의 영향의 최악을 감소시킨 성공적인 완화를 구현했습니다. 그러나 고객의 하위 세트는 관리 콘솔에서 사용되는 데이터 신선도에 대한 데이터 지연을 볼 수 있습니다. 우리는 완전한 완화를 향해 노력합니다.

4. 2026년 7월 17일 AM 1:48 UTCresolved

   문제는 이제 완전히 mitigated이고이 사건은 해결됩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 10일 PM 6:12 UTCidentified

   We identified an issue with one of our infrastructure providers affecting search for a subset of commerce customers in all regions. You may see service unreachable messages at times. Our team is already working on mitigating the impact and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 7월 10일 PM 6:31 UTCidentified

   We've identified that the impact was specifically scoped to Commerce Recommendations and Product Listing Pages. Regular search queries are unaffected. Our team is continuing to work on mitigating the problem and will post regular updates until solved.

3. 2026년 7월 10일 PM 6:54 UTCidentified

   We are seeing a progressive recovery of the issues affecting our infrastructure provider and the errors affecting Commerce Recommendations and Product Listing Pages are also trending down. The incident is still not fully resolved and sporadic errors are still observed at the moment.

4. 2026년 7월 10일 PM 7:50 UTCmonitoring

   The issue affecting Commerce Recommendations and Product Listing Pages has been fixed and we are closely monitoring the service. If you need help or to get in touch with us, please visit our Help Portal

5. 2026년 7월 10일 PM 9:40 UTCresolved

   This incident has been resolved.

1. 2026년 5월 21일 PM 4:16 UTCidentified

   We identified an issue affecting a subset of requests sent to the Commerce Service in all regions. Recommendation requests where a product ID is either null or empty are currently being answered with 422 responses. Other requests are unaffected. Our team is already working on mitigating the impact and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 5월 21일 PM 4:53 UTCmonitoring

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

3. 2026년 5월 21일 PM 5:52 UTCresolved

   This incident has been resolved.

1. 2026년 5월 8일 AM 11:39 UTCidentified

   We're investigating an issue affecting the visibility of Document Logs in the US region. Some Document Logs may currently be unavailable as a result of an outage from one of our infrastructure providers. Our team is investigating potential mitigation actions and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 5월 8일 PM 2:56 UTCidentified

   We've identified the root cause and our team is working towards processing historical data.

3. 2026년 5월 8일 PM 7:03 UTCmonitoring

   Historical data was fully reprocessed, Document Logs are now available as normal. The team is continuing to monitor the service closely.

4. 2026년 5월 8일 PM 7:51 UTCresolved

   This incident has been resolved.

1. 2026년 4월 29일 PM 3:01 UTCidentified

   We've identified an issue delaying ML model builds in the US region. Existing models refresh may fall behind schedule. Our team is investigating and will post regular updates until solved. ML Serving remains unaffected. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 4월 29일 PM 4:31 UTCmonitoring

   A fix has been implemented and we will continue monitoring the results. Thank you for your patience.

3. 2026년 4월 29일 PM 9:31 UTCresolved

   This incident has been resolved.

1. 2026년 4월 27일 PM 8:47 UTCresolved

   Between 1:46PM EDT and 2:47PM EDT, a temporary degradation of the Commerce API occurred which affected response time latency in the US region during that time window. The issue has been fixed and we are closely monitoring the service. If you need help or to get in touch with us, please visit our Help Portal

1. 2026년 4월 8일 PM 7:14 UTCidentified

   We identified an issue affecting Atomic v3 in all regions. Atomic V3 component can have issue loading. Our team is already working on mitigating the impact and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 4월 8일 PM 7:21 UTCmonitoring

   The issue has been fixed and we are actively monitoring this service. Thank you for your patience.

3. 2026년 4월 8일 PM 7:56 UTCresolved

   The service has remained fully operational since the last update. This incident is resolved.

1. 2026년 4월 3일 PM 9:53 UTCinvestigating

   We are investigating an issue affecting the Intent Aware Product Ranking Machine Learning models. Changes in catalogs may not be taken into account in a timely manner. Our team is investigating and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 4월 4일 AM 1:48 UTCmonitoring

   A fix has been implemented and we are monitoring the results. If you need help or to get in touch with us, please visit our Help Portal

3. 2026년 4월 4일 AM 2:33 UTCresolved

   This incident has been resolved.

1. 2026년 3월 27일 AM 2:33 UTCidentified

   We've identified an issue causing content refresh delays in our Australian hosting region. Your content might not be up to date. Our team is working on it and will post updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 3월 27일 AM 3:21 UTCidentified

   The root cause has been identified and a fix is currently being implemented.

3. 2026년 3월 27일 AM 4:04 UTCmonitoring

   A fix has been implemented and we are monitoring the results. Content updates are now being processed again.

4. 2026년 3월 27일 AM 4:16 UTCresolved

   This incident has been resolved. Thank you for your patience.

1. 2026년 3월 4일 AM 6:22 UTCmonitoring

   We have identified an issue causing elevated source job refresh times. A fix has already been implemented and we are monitoring the results.

2. 2026년 3월 4일 AM 6:26 UTCresolved

   This incident has been resolved.

1. 2026년 2월 6일 PM 10:24 UTCinvestigating

   We're currently investigating an issue causing degraded relevance with Automatic Relevance Tuning (ART) in all regions. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 2월 6일 PM 10:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 2월 6일 PM 10:44 UTCidentified

   The cause has been identified and mitigation is in progress. We will provide an update once the situation is fully resolved.

4. 2026년 2월 7일 AM 1:00 UTCmonitoring

   The issue has been fixed. We are monitoring the situation closely to ensure a full recovery.

5. 2026년 2월 7일 AM 2:42 UTCresolved

   This incident has been resolved.

1. 2026년 1월 13일 PM 10:53 UTCmonitoring

   We identified and mitigated an issue affecting the Search Service in all regions. Queries were being throttled due to a system issue. Our team has applied a mitigation and we are actively monitoring this service. Thank you for your patience. If you need help or to get in touch with us, please visit our Help Portal

2. 2026년 1월 13일 PM 11:00 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 2026년 1월 13일 PM 11:31 UTCresolved

   The service has remained fully operational since the last update. This incident is resolved.

1. 2025년 12월 16일 AM 9:37 UTCidentified

   We identified an issue affecting Analytics Ingestion in the EU region. Due to an issue with a third-party infrastructure provider, reporting on analytic data is not currently possible. Our team is already working on mitigating the impact and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2025년 12월 16일 AM 10:18 UTCidentified

   We identified an issue affecting Analytics Ingestion in the EU and US regions. Due to an issue with a third-party infrastructure provider, reporting on analytic data in the EU region is not currently possible. Additionally, Data Share feature for the US West (Oregon) region might be affected. Our team is continuing to work on mitigating the impact and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

3. 2025년 12월 16일 PM 6:07 UTCidentified

   The issue with the third-party infrastructure provider has been resolved, processing of new data is back to normal. Data received during the outage is being processed. Reporting on analytics data in the EU region and Data Share in the US West (Oregon) region is affected. Our team is continuing to work on mitigating the impact and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

4. 2025년 12월 17일 AM 2:20 UTCresolved

   The data received during the third-party outage has been processed. Reporting in EU and Data Share in US West (Oregon) should be back to normal. If you need help or to get in touch with us, please visit our Help Portal

1. 2025년 12월 10일 AM 5:34 UTCidentified

   We're investigating an issue affecting analytics ingestion in the US, Europe and Australia regions. Events are still being ingested but there is increased latency in their processing. Our team is investigating and will post regular updates until solved. If you need help or to get in touch with us, please visit our Help Portal

2. 2025년 12월 10일 AM 6:12 UTCmonitoring

   The issue has been linked to an infrastructure provider and is now fixed. We are actively monitoring this service. Thank you for your patience.

3. 2025년 12월 10일 PM 3:28 UTCresolved

   This incident has been resolved.

1. 2025년 11월 21일 PM 9:15 UTCmonitoring

   As of November 13, 2025, Zscaler reclassified coveo.com as "AI/ML Applications", causing access issues for some customers. This may block Coveo search results and related features. We recommend allow-listing Coveo domains/IPs in Zscaler and reviewing Zscaler's documentation on adding urls to allowlists .  If issues persist, please open a P1 ticket with Zscaler noting this impact. More details: Knowledge Article .

2. 2025년 11월 24일 PM 4:14 UTCresolved

   This incident has been resolved. Zscaler has reclassified coveo.com to "Other Information Technologies", resolving the access issues some customers were experiencing.

1. 2025년 10월 20일 AM 9:50 UTCmonitoring

   An issue with an infrastructure provider has led to a partial degradation of some Coveo services. Mitigations are already ongoing at the level of infrastructure provider and therefore we are already seeing improvements happening. We will continue to monitor the issue until this is fully resolved.

2. 2025년 10월 20일 AM 11:27 UTCmonitoring

   The underlying issues have been resolved by our infrastructure provider. Coveo services have been working normally since the last update and we are working on a document processing backlog that accumulated over the incident in the US region. All other region's document processing is caught up to real time.

3. 2025년 10월 20일 PM 1:11 UTCidentified

   Due to the ongoing issue with our infrastructure provider, we are observing a degradation of Analytics Read services in the US region. Users of this service are currently seeing elevated error rates. We are also continuing to process the previously mentioned document processing backlog.

4. 2025년 10월 20일 PM 1:50 UTCidentified

   All document processing backlogs have been processed, so indexed documents are now up to date for all customers in all regions. We are continuing to see elevated error rates on the Analytics Read service as the issue with our infrastructure provider is ongoing.

5. 2025년 10월 20일 PM 3:11 UTCidentified

   We are continuing to see elevated error rates on the Analytics Read API and are now seeing some delays in Analytics Event Ingestion in the US region. No events are lost, at the moment they are being queued for processing.

6. 2025년 10월 20일 PM 4:29 UTCidentified

   We are continuing to see elevated error rates on the Analytics Read API as well as continued delays in Analytics Event Ingestion in the US region. No events are lost, at the moment they are being queued for processing. Real-time Machine Learning features, such as Personalisation as You Go, are also impacted by the delay in Analytics Ingestion, impacting the quality of the results.

7. 2025년 10월 20일 PM 5:37 UTCidentified

   We are continuing to see elevated error rates on the Analytics Read API as well as continued delays in Analytics Event Ingestion in the US region. No events are lost, at the moment they are being queued for processing. Real-time Machine Learning features, such as Personalisation as You Go, are also impacted by the delay in Analytics Ingestion, impacting the quality of the results. Capacity problems are also slowing down our crawling operations in the US region, introducing some delays for scheduled jobs. Your content for sources crawled by our infrastructure may not be up to date. Push API and Crawling Module sources remain up to date.

8. 2025년 10월 20일 PM 6:39 UTCidentified

   We are continuing to see elevated error rates on the Analytics Read API as well as continued delays in Analytics Event Ingestion in the US region. No events are lost, at the moment they are being queued for processing. Real-time Machine Learning features, such as Personalisation as You Go, are also impacted by the delay in Analytics Ingestion, impacting the quality of the results. Capacity issues have improved in the US region, and Crawling is back to normal operations.

9. 2025년 10월 20일 PM 8:46 UTCidentified

   We are seeing continued delays in Analytics Event Ingestion. No events are lost, at the moment they are being queued for processing. Real-time Machine Learning features, such as Personalisation as You Go, are also impacted by the delay in Analytics Ingestion, impacting the quality of the results. The elevated error rates which impacted the Analytics Read API in the last few hours have been mitigated and that service is now back to normal operations.

10. 2025년 10월 20일 PM 9:42 UTCmonitoring

    All remaining impacted services have returned to normal operations since the last update. The Analytics Event Ingestion backlog has been processed, and the Real-Time Machine Learning features that depend on them are now all caught up. We are continuing to monitor all services closely.

11. 2025년 10월 21일 AM 11:29 UTCresolved

    This incident has been resolved. All services have remained fully operational since the last update.