Clari Outage History

Clari is up right now

Clari had 27 outages in the last 2 years totaling 33h 54m of downtime — averaging 1.1 incidents per month.

There were 27 Clari outages since June 10, 2025 totaling 33h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://clari.statuspage.io

Minor June 12, 2025

Groove is not working as expected

Detected by Pingoru
Jun 12, 2025, 06:42 PM UTC
Resolved
Jun 12, 2025, 07:36 PM UTC
Duration
54m
Affected: Groove webappGroove Extension
Timeline · 4 updates
  1. investigating Jun 12, 2025, 06:42 PM UTC

    We're currently experiencing an issue with our third party providers - https://status.firebase.google.com. Some of Groove services are impacted and won't function properly. Our team is actively investigating.

  2. monitoring Jun 12, 2025, 06:56 PM UTC

    Groove is back to being operational. We're still monitoring Google Cloud https://status.cloud.google.com/ to ensure to ensure all related Groove services are up and running.

  3. resolved Jun 12, 2025, 07:36 PM UTC

    This incident has been resolved.

  4. postmortem Jun 17, 2025, 08:24 PM UTC

    On 2025-06-12 between 18:00 and 19:36 UTC, Groove experienced a significant service disruption due to an outage affecting Google Cloud. The underlying issue was reported by Google and is detailed on their status page, [https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW](https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW). ‌ During the outage, the Groove platform was largely inaccessible to users. Attempts to log in to Groove failed, resulting in a full loss of access across key services including the Groove Web App, Groove Dialer, and Groove Chrome Extension. As a result, users were unable to complete workflows or retrieve data. ‌ Once Google resolved the root cause of their service disruption, Groove systems automatically recovered. After closely monitoring performance during peak usage, Clari formally marked the incident as resolved at 21:00 UTC on June 12, 2025.

Read the full incident report →

Minor June 10, 2025

Copilot MS Teams recordings experiencing elevated failures

Detected by Pingoru
Jun 10, 2025, 09:14 AM UTC
Resolved
Jun 11, 2025, 06:15 PM UTC
Duration
1d 9h
Affected: Clari Copilot
Timeline · 7 updates
  1. investigating Jun 10, 2025, 09:14 AM UTC

    MS Teams recordings are experiencing higher than expected error rates. Our engineering team is actively investigating.

  2. identified Jun 10, 2025, 11:18 AM UTC

    Our engineering team has identified the issue and implemented a fix. Microsoft Teams calls are now being recorded. However, users may still experience degraded recording quality. We are actively working to restore full recording quality and will share further updates once the improvements have been deployed. The next update will be provided after the fix has been applied.

  3. monitoring Jun 10, 2025, 03:50 PM UTC

    Video quality issue affecting Microsoft Teams call recordings has been resolved. Recordings are now being captured with expected video quality in Copilot. Our engineering team is currently focused on addressing an issue with speaker identification, where speakers may not be accurately recognised in recorded meetings. The next status update will be when speaker identification issue is addressed.

  4. monitoring Jun 11, 2025, 02:43 AM UTC

    Our engineering team is actively investigating the issue with speaker identification and is working to resolve it. The next update will be shared once more information is available or the issue is resolved.

  5. monitoring Jun 11, 2025, 02:55 PM UTC

    Our engineering team has made progress in addressing the speaker identification issue. Approximately two-thirds of recorded Microsoft Teams calls now correctly identify speakers. Investigations are ongoing to improve speaker identification for the remaining calls. Further updates will be shared as more information becomes available or once the issue is fully resolved.

  6. resolved Jun 11, 2025, 06:15 PM UTC

    We have confirmed the issue with speaker identification in Microsoft Teams call recordings has been fully resolved. All calls are now identifying speakers. A summary of the incident will be posted within the next three US business days.

  7. postmortem Jun 15, 2025, 04:19 AM UTC

    On 2025-06-09 at 19:30 UTC, Clari detected an issue caused by a change in the Microsoft Teams Web UI which impacted Copilot’s ability to record calls. The recording functionality was restored by 2025-06-10 11:18 UTC. However, speaker identification was still not functioning correctly. A subsequent fix was deployed, and full functionality, including accurate speaker identification, was restored by 2025-06-11 18:15 UTC. Microsoft Teams calls scheduled between the impact time and initial fix were not recorded. All Zoom and Google Meet calls scheduled during this period were recorded successfully and were unaffected.

Read the full incident report →