Coveo Cloud incident

All Regions - Commerce Search Issues

Major Resolved View vendor source →

Coveo Cloud experienced a major incident on July 10, 2026 affecting Search - Search Service and Search - Search Service and 1 more component, lasting 3h 28m. The incident has been resolved; the full update timeline is below.

Started
Jul 10, 2026, 06:12 PM UTC
Resolved
Jul 10, 2026, 09:40 PM UTC
Duration
3h 28m
Detected by Pingoru
Jul 10, 2026, 06:12 PM UTC

Affected components

Search - Search ServiceSearch - Search ServiceSearch - Search ServiceSearch - Search ServicePlatform - Customer Service APIPlatform - Customer Service APIPlatform - Customer Service APIPlatform - Customer Service API

Update timeline

  1. identified Jul 10, 2026, 06:12 PM UTC

    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. identified Jul 10, 2026, 06:31 PM UTC

    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. identified Jul 10, 2026, 06:54 PM UTC

    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. monitoring Jul 10, 2026, 07:50 PM UTC

    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. resolved Jul 10, 2026, 09:40 PM UTC

    This incident has been resolved.