Vendor Status Watch

← all vendors

Coveo Cloud status history

Current state: operational — “All Systems Operational” per https://status.cloud.coveo.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
6incidents, last 90 days
25incidents on record
Incidents per week, last 12 weeks:

How long do Coveo Cloud incidents last?

115 minmedian incident duration25 measured
16.7 h90th percentile1 in 10 ran longer
111 minmedian, major/critical only8 incidents

From 25 incidents with a vendor-posted start and resolve time. Longest on record: Zscaler Classification Impact — 2.8 days (2025-11-21 21:15 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (25)

StartedIncidentStatusImpactDuration
2026-08-26 19:12 UTC[All Regions] Hosted Search Pages issueresolvedcritical1 h 05 min
2026-08-18 16:34 UTC[US] Group Invite Issuesresolvednone35 min
2026-08-04 20:16 UTCUS - Generative Answering Issuesresolvedmajor4 h 32 min
2026-07-17 12:05 UTC[All Regions] Commerce Search Issuesresolvedminor1 h 50 min
2026-07-16 10:56 UTC[US] Analytics Reporting and ML Model Issuesresolvedminor14 h 51 min
2026-07-10 18:12 UTCAll Regions - Commerce Search Issuesresolvedmajor3 h 28 min
2026-05-21 16:16 UTC[All Regions] Commerce Service Issuesresolvedminor1 h 35 min
2026-05-08 11:39 UTC[US] Document Log Visibility Issuesresolvednone8 h 11 min
2026-04-29 15:01 UTC[US] ML Model Building Issueresolvedminor6 h 29 min
2026-04-27 17:46 UTC[US] Commerce API latencyresolvednone0 min
2026-04-08 19:14 UTC[All Regions] Atomic v3 Issuesresolvedminor41 min
2026-04-03 21:53 UTC[All Regions] Intent Aware Product Ranking Issuesresolvedminor4 h 39 min
2026-03-27 02:33 UTC[Australia] Content Refresh Delaysresolvedmajor1 h 42 min
2026-03-04 06:22 UTC[US] Elevated source job refresh timesresolvedminor3 min
2026-02-06 22:24 UTC[All Regions] Automatic Relevance Tuning Issueresolvedminor4 h 17 min
2026-01-13 22:53 UTC[All Regions] Search Service Issuesresolvedminor37 min
2025-12-16 09:37 UTC[US] [EU] Analytics Ingestion Issuesresolvedmajor16 h 43 min
2025-12-10 05:34 UTC[US] [EU] [AU] Analytics Ingestion Delayresolvedminor9 h 53 min
2025-11-21 21:15 UTCZscaler Classification Impactresolvednone2 d 18 h
2025-10-20 09:50 UTC[All Regions] Infrastructure provider issueresolvedminor25 h 38 min
2025-10-08 19:01 UTC[All Regions] Crawling Issuesresolvedmajor1 h 38 min
2025-10-07 14:45 UTC[EU] Coveo Experimentation Hub Issuesresolvednone41 min
2025-10-06 21:08 UTC[All Regions] Search Issuesresolvedmajor2 h 00 min
2025-10-02 03:06 UTC[US] [CA] [AU] Indexing Pipeline Issuesresolvedmajor54 min
2025-09-18 09:48 UTC[Europe] Reduced Performance for Commerce Queriesresolvedminor1 h 55 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Coveo Cloud with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "coveo-cloud"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}