Historique des pannes de Coveo Cloud

1. 26 août 2026 à 19:12 UTCinvestigating

   Nous enquêtons actuellement sur un problème touchant les pages de recherche en utilisant le constructeur hébergé dans toutes les régions. Ces pages sont actuellement indisponibles. Notre équipe enquête et affichera des mises à jour régulières jusqu'à ce que résolu.

2. 26 août 2026 à 19:25 UTCmonitoring

   Une correction a été mise en place et toutes les pages de recherche hébergées sont maintenant opérationnelles. Nous continuerons de suivre de près la situation.

3. 26 août 2026 à 20:17 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 18 août 2026 à 16:34 UTCidentified

   Nous avons identifié un problème touchant les invités du Groupe dans la région des États-Unis. Les clients pourraient ne pas être en mesure d'inviter un nouvel utilisateur à leur organisation. Notre équipe travaille déjà sur l'atténuation de l'impact et affichera régulièrement des mises à jour jusqu'à ce que résolu. Si vous avez besoin d'aide ou pour nous contacter, veuillez consulter notre portail d'aide

2. 18 août 2026 à 16:52 UTCmonitoring

   Le problème a été résolu et nous suivons activement ce service. Merci de votre patience.

3. 18 août 2026 à 17:10 UTCresolved

   Le service est resté pleinement opérationnel depuis la dernière mise à jour. Cet incident est résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 4 août 2026 à 20: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. 4 août 2026 à 21: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. 5 août 2026 à 00: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. 17 juillet 2026 à 12:05 UTCinvestigating

   Nous enquêtons sur un problème touchant le Commerce Search. Pour un sous-ensemble de clients, certains champs qui existaient auparavant peuvent être absents des champs supplémentaires dans les réponses API Commerce. Notre équipe enquête et affichera des mises à jour régulières jusqu'à ce que résolu. Si vous avez besoin d'aide ou pour nous contacter, veuillez consulter notre portail d'aide

2. 17 juillet 2026 à 12:26 UTCidentified

   La cause fondamentale a été identifiée et notre équipe s'efforce d'atténuer le problème.

3. 17 juillet 2026 à 12:48 UTCidentified

   Nous avons identifié une solution et nous nous attendons à ce que la question soit atténuée dans une heure. Les clients s'appuyant sur les champs standard existant dans l'objet des champs additionnels sont touchés. On peut régler cette question en s'appuyant directement sur les champs standard eux-mêmes, plutôt que de les utiliser via des champs supplémentaires

4. 17 juillet 2026 à 13:16 UTCmonitoring

   Le correctif a été mis en œuvre et confirmé pour fonctionner, en éliminant l'impact. Nous continuons de surveiller le service.

5. 17 juillet 2026 à 13:55 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 juillet 2026 à 10:56 UTCidentified

   Nous avons relevé un problème touchant les rapports analytiques et un sous-ensemble de modèles ML dans la région américaine. Ceci empêche les mises à jour de nos partages de données et de nos rapports de plateforme. Les données observées peuvent être retardées. Notre équipe travaille déjà sur l'atténuation de l'impact et affichera régulièrement des mises à jour jusqu'à ce que résolu. Si vous avez besoin d'aide ou pour nous contacter, veuillez consulter notre portail d'aide

2. 16 juillet 2026 à 16:07 UTCidentified

   Nous avons identifié la cause fondamentale et notre équipe travaille toujours activement à résoudre le problème.

3. 17 juillet 2026 à 01:15 UTCidentified

   Notre équipe a mis en place des mesures d'atténuation efficaces qui ont réduit le pire de l'impact dans la plupart des cas. Cependant, un sous-ensemble de clients continuera de constater des retards dans la fraîcheur des données utilisées dans la Console d'administration. Nous continuons de travailler à l'atténuation complète.

4. 17 juillet 2026 à 01:48 UTCresolved

   La question est maintenant entièrement atténuée et cet incident est résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 10 juillet 2026 à 18: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. 10 juillet 2026 à 18: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. 10 juillet 2026 à 18: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. 10 juillet 2026 à 19: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. 10 juillet 2026 à 21:40 UTCresolved

   This incident has been resolved.

1. 21 mai 2026 à 16: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. 21 mai 2026 à 16:53 UTCmonitoring

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

3. 21 mai 2026 à 17:52 UTCresolved

   This incident has been resolved.

1. 8 mai 2026 à 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. 8 mai 2026 à 14:56 UTCidentified

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

3. 8 mai 2026 à 19:03 UTCmonitoring

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

4. 8 mai 2026 à 19:51 UTCresolved

   This incident has been resolved.

1. 29 avril 2026 à 15: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. 29 avril 2026 à 16:31 UTCmonitoring

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

3. 29 avril 2026 à 21:31 UTCresolved

   This incident has been resolved.

1. 27 avril 2026 à 20: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. 8 avril 2026 à 19: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. 8 avril 2026 à 19:21 UTCmonitoring

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

3. 8 avril 2026 à 19:56 UTCresolved

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

1. 3 avril 2026 à 21: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. 4 avril 2026 à 01: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. 4 avril 2026 à 02:33 UTCresolved

   This incident has been resolved.

1. 27 mars 2026 à 02: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. 27 mars 2026 à 03:21 UTCidentified

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

3. 27 mars 2026 à 04:04 UTCmonitoring

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

4. 27 mars 2026 à 04:16 UTCresolved

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

1. 4 mars 2026 à 06: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. 4 mars 2026 à 06:26 UTCresolved

   This incident has been resolved.

1. 6 février 2026 à 22: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. 6 février 2026 à 22:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 février 2026 à 22:44 UTCidentified

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

4. 7 février 2026 à 01:00 UTCmonitoring

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

5. 7 février 2026 à 02:42 UTCresolved

   This incident has been resolved.

1. 13 janvier 2026 à 22: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. 13 janvier 2026 à 23:00 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 13 janvier 2026 à 23:31 UTCresolved

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

1. 16 décembre 2025 à 09: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. 16 décembre 2025 à 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. 16 décembre 2025 à 18: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. 17 décembre 2025 à 02: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. 10 décembre 2025 à 05: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. 10 décembre 2025 à 06: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. 10 décembre 2025 à 15:28 UTCresolved

   This incident has been resolved.

1. 21 novembre 2025 à 21: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. 24 novembre 2025 à 16: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. 20 octobre 2025 à 09: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. 20 octobre 2025 à 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. 20 octobre 2025 à 13: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. 20 octobre 2025 à 13: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. 20 octobre 2025 à 15: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. 20 octobre 2025 à 16: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. 20 octobre 2025 à 17: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. 20 octobre 2025 à 18: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. 20 octobre 2025 à 20: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. 20 octobre 2025 à 21: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. 21 octobre 2025 à 11:29 UTCresolved

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