Clari Outage History

Started Dec 18, 2025, 02:08 PM UTC· resolved Dec 18, 2025, 04:47 PM UTC

1. investigating Dec 18, 2025, 02:08 PM UTC

   Copilot is not recording some calls. Our engineering team is actively investigating.

2. identified Dec 18, 2025, 02:56 PM UTC

   Our engineering teams have identified the issue and are working to restore the capability to record Google Meet meetings. The next status update will be after the fix has been applied.

3. resolved Dec 18, 2025, 04:47 PM UTC

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

4. postmortem Dec 22, 2025, 05:10 PM UTC

   On 2025-12-18 at approximately 12:00 UTC, a change by Google to the Google Meet web UI began to be rolled out that affected Copilot’s ability to record calls for a subset of customers using Google Meets. Between 13:05 UTC and 14:20 UTC some calls with MS Teams and Zoom were also impacted and not recorded. Clari made an update to Copilot to account for the updated UI and recording functionality was fully restored by 2025-12-18 at 16:45 UTC. For the impacted customers, calls scheduled during this period were not recorded.

Read the full incident report →

Started Dec 16, 2025, 08:46 PM UTC· resolved Dec 16, 2025, 11:18 PM UTC

1. investigating Dec 16, 2025, 08:46 PM UTC

   Some customers may be experiencing degraded performance or partial outages with Forecast and Inspect. Our engineering team is actively investigating.

2. monitoring Dec 16, 2025, 10:05 PM UTC

   Our engineering teams have mitigated the issue and we are monitoring the fix.

3. resolved Dec 16, 2025, 11:18 PM UTC

   We have confirmed the issue has been resolved for the impacted users.

Read the full incident report →

Started Dec 12, 2025, 03:26 PM UTC· resolved Dec 12, 2025, 06:34 PM UTC

1. investigating Dec 12, 2025, 03:26 PM UTC

   Some Google Meet calls that are recorded with Copilot recorder are returning an error and not being recorded successfully. Our engineering team is actively investigating the issue.

2. identified Dec 12, 2025, 04:40 PM UTC

   Our engineering teams have identified the issue and are implementing a fix. The next status update will be after the fix has been applied.

3. monitoring Dec 12, 2025, 06:02 PM UTC

   Our engineering teams have resolved the issue and we are monitoring the fix.

4. resolved Dec 12, 2025, 06:34 PM UTC

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

5. postmortem Dec 16, 2025, 10:48 PM UTC

   On 2025-12-11 at approximately 23:00 UTC, a change by Google to the Google Meet web UI began to be rolled out that affected Copilot’s ability to record calls for a subset of customers. Clari made an update to Copilot to account for the updated UI and recording functionality was fully restored by 2025-12-13 at 18:35 UTC. For a small subset of customers, Google Meet calls scheduled during this period were not recorded. All Zoom and Microsoft Teams calls continued to record successfully and were unaffected.

Read the full incident report →

Started Dec 09, 2025, 01:48 PM UTC· resolved Dec 10, 2025, 12:02 PM UTC

1. investigating Dec 09, 2025, 01:48 PM UTC

   Multiple customers impacted by a lag in entity loading to RevDB Our engineering team is actively investigating.

2. investigating Dec 09, 2025, 03:14 PM UTC

   We are continuing to investigate the cause of the delay. Customers can expect data displayed to be up to 3-4hrs stale.

3. monitoring Dec 09, 2025, 04:22 PM UTC

   Our engineering teams have implemented a fix. We are now working to remediate the remaining effects of the incident. The next status update will be when remediation efforts are complete or the state of this incident otherwise changes.

4. monitoring Dec 09, 2025, 11:46 PM UTC

   Our engineering teams have addressed the immediate causes of data lag. We will be monitoring the system to ensure there is no continued impact.

5. resolved Dec 10, 2025, 12:02 PM UTC

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

6. postmortem Dec 12, 2025, 06:26 PM UTC

   Between 2025-12-09 11:08:00 UTC and 2025-12-09 16:25:26 UTC Clari experienced a delay in synchronization of CRM data to RevDB. Customers saw stale data and degraded performance of Clari Web Application. The issue was caused due to a database contention and was resolved by identifying and fixing the source of blocking queries. After the fix we monitored the database and after observing stable performance for a period of time it was confirmed that the issue was fully resolved. No user data was at risk or damaged by this incident.

Read the full incident report →

Started Oct 29, 2025, 05:29 PM UTC· resolved Oct 30, 2025, 01:03 AM UTC

1. investigating Oct 29, 2025, 05:29 PM UTC

   Please follow https://azure.status.microsoft/en-gb/status for updates.

2. monitoring Oct 29, 2025, 08:30 PM UTC

   After Microsoft restored their services to a last known good configuration, some users are seeing recovery. We will continue to monitor the external Azure incident.

3. resolved Oct 30, 2025, 01:03 AM UTC

   Microsoft has reported complete resolution and add-in functionality has been restored.

4. postmortem Nov 08, 2025, 01:11 AM UTC

   Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, Clari customers were not able to use the Groove Outlook Add-in due to a Microsoft Azure outage. See the Microsoft Azure status page for full details, [https://azure.status.microsoft/en-us/status/history](https://azure.status.microsoft/en-us/status/history). The Azure service was restored at 00:05 UTC on 30 October 2025, at which time the Groove Outlook Add-in returned to normal functionality. No customer data was at risk during this incident.

Read the full incident report →

Started Oct 21, 2025, 04:10 PM UTC· resolved Oct 21, 2025, 06:43 PM UTC

1. investigating Oct 21, 2025, 04:10 PM UTC

   Clari's RevDB pipelines are currently delayed. This can lead to stale data for any feature utilizing RevDB data. We are currently investigating and will post an update within 30 minutes

2. monitoring Oct 21, 2025, 04:41 PM UTC

   After manual intervention, we are seeing improvement in delays around RevDB data. We will continue to monitor the state of the system and will post an update within 30 minutes

3. monitoring Oct 21, 2025, 05:16 PM UTC

   We continue to see improvement in delays around RevDB data, but they are not yet within normal operating values. We will continue to monitor the state of the system and will post an update within 30 minutes

4. monitoring Oct 21, 2025, 05:44 PM UTC

   The majority of users' RevDB data delays are now within normal operating values, but not all have fully recovered. We will continue to monitor the state of the system and will post and update within 60 minutes

5. resolved Oct 21, 2025, 06:43 PM UTC

   All RevDB pipelines are showing as healthy, with metrics in normal operating values.

Read the full incident report →

Started Oct 20, 2025, 08:11 AM UTC· resolved Oct 21, 2025, 01:03 PM UTC

1. identified Oct 20, 2025, 08:11 AM UTC

   We are observing a wide system stability impact from degraded services on Amazon AWS. Clari services are impacted partially due to this. We are actively monitoring the situation and will be sharing updates.

2. investigating Oct 20, 2025, 08:21 AM UTC

   We are observing a wide system stability impact from degraded services on Amazon AWS. Clari services are impacted partially due to this. We are actively monitoring the situation and will be sharing updates. The following Clari Platform components are affected: Clari, Groove Dialer, Copilot.

3. investigating Oct 20, 2025, 08:52 AM UTC

   At this time we are experiencing outages across multiple product lines due to an ongoing AWS incident (https://health.aws.amazon.com/health/status). We are actively monitoring the situation and will be sharing updates. The following Clari Platform components are affected: Clari, Groove Dialer, Copilot.

4. monitoring Oct 20, 2025, 11:17 AM UTC

   AWS confirms that they have resolved the primary cause of the outage (https://health.aws.amazon.com/health/status), however there still exist a problem with launching additional compute capacity. As a result: - Clari Core is fully operational, but we will continue to monitor throughout the day for signs of degraded performance due to potential inablity to scale up - Clari Copilot is still degraded and most of the calls do not have Copilot joining them due to lack of available compute capacity - Groove Dialer is still degraded due to downstream (Twillio) service being degraded. We will continue to monitor system recovery throughout the day and will post updates as status changes.

5. monitoring Oct 20, 2025, 02:05 PM UTC

   We continue to monitor the recovery of our systems following AWS outage (https://health.aws.amazon.com/health/status). While the root cause has been addressed, we are still having troubles leasing additional compute capacity. As a result: - Clari Core is fully functional. We are monitoring system vitals. - Clari Copilot is slowly recovering, but we are still observing that approximately half of Recorder bots are missing meetings or are late to join it. - Groove, including Groove Dialer is fully functional. We are monitoring system vitals

6. monitoring Oct 20, 2025, 02:21 PM UTC

   Increased traffic combined with inability to scale-up due to underlying issue with our Cloud Service Provider is impacting Clari-Core services with increasing error rates and latencies. Similarly, Clari-Copilot is experiencing delayed Recorder bots

7. monitoring Oct 20, 2025, 03:29 PM UTC

   As a result of underlying Cloud Provider Incident (https://health.aws.amazon.com/health/status) we are observing gradual service degradation across all Clari products: - Clari Platform users will experience increased error rate and latencies - Groove users may experience increased error rates and latencies - Copilot Recorder bots are unable to join the calls. We continue to monitor underlying AWS service degradation and we will post updates

8. monitoring Oct 20, 2025, 04:05 PM UTC

   We continue to monitor an underlying Cloud Provider Incident (https://health.aws.amazon.com/health/status). We are observing service degradation across all Clari products: - Clari Platform users are experiencing increased error rate and latencies - Groove users users are experiencing increased error rates and latencies - Copilot Recorder bots are unable to join the calls.

9. monitoring Oct 20, 2025, 05:36 PM UTC

   We continue to monitor an underlying Cloud Provider Incident (https://health.aws.amazon.com/health/status). We are observing service degradation across all Clari products: - Clari Platform users are experiencing increased error rate and latencies - Groove users users are experiencing increased error rates and latencies - Copilot Recorder bots are unable to join the calls. We will continue posting updates as the situation progresses.

10. monitoring Oct 20, 2025, 06:31 PM UTC

    Mitigations are being rolled out in the underlying Cloud Provider Incident(https://health.aws.amazon.com/health/status). As our services recover capacity, there may be some inconsistencies in configuration. These effects are temporary and will resolve as our other upstream vendors recover from the Cloud outage. We are still observing service degradation across all Clari Products. We will continue posting updates as the situation progresses.

11. monitoring Oct 20, 2025, 11:28 PM UTC

    The underlying Cloud Provider Incident has been resolved, however other upstream service providers continue to experience high error rates. We are still observing service degradation across all Clari Products. We will continue posting updates as the situation progresses.

12. monitoring Oct 21, 2025, 04:19 AM UTC

    We are still experiencing elevated errors from an upstream service providers. Error rates continue to improve, but we are still observing some service degradation across all Clari Products. We will continue posting updates as the situation progresses

13. monitoring Oct 21, 2025, 08:28 AM UTC

    Both upstream incidents have been mitigated by the providers (Launch Darkly reports their fix is in place and under observation). Our systems have recovered and are operating normally. We are keeping heightened monitoring in place across all services. If we detect any regression, we’ll update this incident.

14. resolved Oct 21, 2025, 01:03 PM UTC

    We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

15. postmortem Oct 24, 2025, 02:29 PM UTC

    On October 20th 2025, 8:11 UTC Clari experienced widespread service degradation across multiple products, including Clari Copilot, Clari Revenue Platform, and Groove services. The disruption was triggered by a major outage in Amazon Web Services \([https://aws.amazon.com/message/101925/\)](https://aws.amazon.com/message/101925/) further compounded by cascading failures in upstream dependencies, including several external service providers that were also impacted by the AWS outage. As AWS and these service providers recovered, Clari systems gradually regained stability. All services were confirmed fully operational by October 21st 2025, 13:03 UTC, after a sustained period of monitoring.

Read the full incident report →

Started Oct 10, 2025, 04:59 PM UTC· resolved Oct 10, 2025, 05:43 PM UTC

1. investigating Oct 10, 2025, 04:59 PM UTC

   We are currently investigating this issue.

2. investigating Oct 10, 2025, 05:00 PM UTC

   We are continuing to investigate this issue.

3. resolved Oct 10, 2025, 05:43 PM UTC

   The issue has been resolved. A summary of the incident will be posted within the next three US business days

4. postmortem Oct 28, 2025, 02:53 PM UTC

   On Friday October 10th, during our Copilot authentication migration, we made network changes that were inadvertently applied in a temporary state. When that state reverted, we lost connectivity to the migrated auth service. This was a one-time activity, and we’ve updated our procedures and system controls to prevent a recurrence

Read the full incident report →

Started Aug 14, 2025, 07:16 PM UTC· resolved Aug 14, 2025, 09:53 PM UTC

1. investigating Aug 14, 2025, 07:16 PM UTC

   Issue with managed package which caused a modification to task record types. If your team is using your own standard or custom record types for the Task object, there should be no impact to users on Groove. You may see changes in any reports or other components that are interacting with Task Record Types.

2. resolved Aug 14, 2025, 09:53 PM UTC

   The issue has been resolved.

Read the full incident report →

Started Aug 14, 2025, 02:28 PM UTC· resolved Aug 14, 2025, 03:36 PM UTC

1. investigating Aug 14, 2025, 02:28 PM UTC

   The integration that syncs new Google Calendar events into Groove is not processing new events. The engineering team is currently investigating the problem.

2. resolved Aug 14, 2025, 03:36 PM UTC

   Our engineering teams have implemented a fix and the problem is resolved. We are now working to remediate the remaining effects of the incident - within the next couple of hours all events from Google Calendar will be synced into Groove. We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

3. postmortem Aug 18, 2025, 06:27 PM UTC

   On 2025-08-14 14:09:39 UTC, we identified an issue that temporarily prevented new Google Calendar events from syncing with Groove. The Clari Engineering team traced the issue to a recent change and reverted it at 2025-08-14 15:10:41 UTC, which resolved the technical issue. Following the fix, synchronization resumed and affected events in the queue gradually propagated. By 2025-08-14 21:11:23 UTC, all impacted events had been successfully synchronized and were visible in Groove. Other areas of the Clari Platform were unaffected. No customer data was impacted or lost as a result of this incident.

Read the full incident report →

Started Aug 13, 2025, 11:47 AM UTC· resolved Aug 13, 2025, 12:22 PM UTC

1. investigating Aug 13, 2025, 11:47 AM UTC

   The Support Center and Knowledge Base are not accessible to customers. Our engineering team is actively investigating the issue.

2. monitoring Aug 13, 2025, 12:13 PM UTC

   Our engineering teams have resolved the issue and we are monitoring the fix.

3. resolved Aug 13, 2025, 12:22 PM UTC

   The issue is resolved. Customers can access the Support Center and Knowledge Base now. A summary of the incident will be posted within the next three US business days.

4. postmortem Aug 14, 2025, 06:28 PM UTC

   On 2025-08-13 at 11:13:50 UTC, the Clari team detected an issue that prevented users from being able to log into the Knowledge Center or contact Clari Support through the Support Portal. The Clari Engineering team reverted a recent change which resolved the issue and the ability to contact Support was restored at 2025-08-13 14:06:00 UTC. Other areas of the Clari Platform were unaffected. No customer data was impacted or lost as a result of this incident.

Read the full incident report →

Started Jul 22, 2025, 11:59 AM UTC· resolved Jul 22, 2025, 02:30 PM UTC

1. investigating Jul 22, 2025, 11:59 AM UTC

   Google Meet recordings are experiencing higher than expected error rates. Our engineering team is actively investigating.

2. resolved Jul 22, 2025, 02:30 PM UTC

   Our engineering team identified the issue and has released a fix. Google Meet calls are now being recorded as expected. A summary of the incident will be posted within the next three US business days.

3. postmortem Jul 26, 2025, 11:18 AM UTC

   On 2025-07-21 at 23:30 UTC, Clari detected an issue caused by a change in the Google Meet web UI that affected Copilot’s ability to record calls. A partial outage began around 2025-07-21 at 21:00 UTC. The recording functionality was fully restored by 2025-07-22 at 14:32 UTC. Google Meet calls scheduled during this period were not recorded. All Zoom and Microsoft Teams calls continued to record successfully and were unaffected.

Read the full incident report →

Started Jul 21, 2025, 02:52 PM UTC· resolved Jul 21, 2025, 03:53 PM UTC

1. investigating Jul 21, 2025, 02:52 PM UTC

   We are currently experiencing issues with staying logged in to the Clari platform and our engineering team is actively investigating it. We will provide further updates as we learn more.

2. investigating Jul 21, 2025, 03:30 PM UTC

   We've noticed recovery in the login service and many of the users are now able to login. The engineering team is working on further remedy.

3. resolved Jul 21, 2025, 03:53 PM UTC

   We have confirmed the issue has been resolved for the impacted users. Our teams are still continuing to monitor the situation to ensure full stability.

4. postmortem Jul 23, 2025, 05:00 PM UTC

   On 2025-07-21 at 13:59 UTC, we detected elevated error rates in our authentication service, causing some users to be automatically logged out. The issue was resolved by increasing the rate limit with our auth provider, and service was fully restored by 15:37 UTC. No customer data was impacted or lost as a result of this incident.

Read the full incident report →

Started Jun 12, 2025, 06:42 PM UTC· resolved Jun 12, 2025, 07:36 PM UTC

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 →

Started Jun 10, 2025, 09:14 AM UTC· resolved Jun 11, 2025, 06:15 PM UTC

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 →

Started May 22, 2025, 03:59 PM UTC· resolved May 22, 2025, 05:45 PM UTC

1. investigating May 22, 2025, 03:59 PM UTC

   Some customers may be seeing problems with Desktop Outlook Add-In. Our engineering team is actively investigating.

2. investigating May 22, 2025, 04:40 PM UTC

   We’re aware that the Outlook Add‑In on both desktop and web may intermittently appear blank. We're currently investigating the issue, and will provide an update soon.

3. monitoring May 22, 2025, 05:16 PM UTC

   Our engineering teams have resolved the issue and we are monitoring the fix.

4. resolved May 22, 2025, 05:45 PM UTC

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

5. postmortem May 23, 2025, 09:50 PM UTC

   On May 22, 2025, between 15:51 and 16:42 UTC, some users experienced a blank Groove Task Pane when accessing the Outlook Add-In via both Desktop and Web. The issue was isolated to users on slower network connections, and not all customers were affected. Our team identified the root cause and implemented a fix, restoring full functionality. We apologize for the disruption and appreciate your patience as we worked to resolve the issue.

Read the full incident report →

Started May 20, 2025, 05:21 PM UTC· resolved May 20, 2025, 05:42 PM UTC

1. investigating May 20, 2025, 05:21 PM UTC

   Some users are currently unable to access the Opportunities module in the Clari app. Our team is actively investigating the issue.

2. resolved May 20, 2025, 05:42 PM UTC

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

3. postmortem May 21, 2025, 10:46 PM UTC

   On 2025-05-20 at 17:01 UTC Clari received reports that the Opportunities module was not loading. It was found that users whose default view was not set to the Opportunities module were unable to access Opportunities. At 17:42 UTC Clari rolled back a change which restored service for all users. Approximately 10% of Clari Core customers were affected. No customer data was impacted or lost as a result of this incident.

Read the full incident report →

Started May 09, 2025, 03:45 PM UTC· resolved May 09, 2025, 08:56 PM UTC

1. monitoring May 09, 2025, 06:55 PM UTC

   Some copilot customers with high call volumes may have seen delays of up to 4 hours before their recordings became available. This issue is now resolved.

2. resolved May 09, 2025, 06:56 PM UTC

   Issue is resolved.

3. postmortem May 09, 2025, 10:11 PM UTC

   Starting at approximately 15:45 UTC on 2025-05-09 the processing of approximately 10% of Copilot recordings was delayed up to 4 hours. This was caused by a heavy call volume creating resource contention. The incident was resolved by expanding our cloud processing capacity resulting in all recordings being processed and available by 20:56 UTC the same day. No customer or call data was lost.

Read the full incident report →

Started May 06, 2025, 11:00 PM UTC· resolved May 07, 2025, 12:30 AM UTC

1. investigating May 06, 2025, 11:00 PM UTC

   We have detected delays in RevDB data pipelines that are affecting many (though not all) customers. This will cause data to become stale in RevDB-powered features, which includes Analyze and Account Inspection for all customers, and Opportunity Inspection and Forecast for many customers. The Clari engineering team is actively working on the issue and will provide regular updates.

2. monitoring May 07, 2025, 12:18 AM UTC

   The team has identified the issue, and applied the fix. We are currently monitoring.

3. resolved May 07, 2025, 12:30 AM UTC

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

4. postmortem May 13, 2025, 04:31 PM UTC

   On 2025-06-06 approximately 17:30 UTC, Clari detected that RevDB data was delayed for 70% of customers, leading to data becoming stale in RevDB-powered features such as Analyze and Account Inspection. RevDB data caught up for all customers by 2025-05-07 1:00 UTC.

Read the full incident report →

Started Apr 07, 2025, 10:26 PM UTC· resolved Apr 08, 2025, 02:28 PM UTC

1. investigating Apr 07, 2025, 10:26 PM UTC

   Some customers may be seeing problems with using Groove Scheduler for Groove Extension and Groove Outlook Add-In. Our engineering team is actively investigating.

2. monitoring Apr 07, 2025, 10:48 PM UTC

   Our engineering teams have implemented a fix. We are now working to remediate the remaining effects of the incident. The next status update will be when remediation efforts are complete or the state of this incident otherwise changes.

3. monitoring Apr 08, 2025, 01:39 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Apr 08, 2025, 02:28 PM UTC

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

5. postmortem Apr 09, 2025, 03:06 PM UTC

   On April 7, 2025, at 20:35 UTC, Groove Scheduler experienced intermittent availability due to an increase in traffic. Our engineering team promptly implemented the necessary adjustments to accommodate the surge. Service was fully restored by 20:48 UTC. At no time during this incident was user data at risk.

Read the full incident report →

Started Apr 07, 2025, 06:11 PM UTC· resolved Apr 07, 2025, 07:08 PM UTC

1. investigating Apr 07, 2025, 06:11 PM UTC

   Google Meet recordings are experiencing higher than expected error rates. Our engineering team is actively investigating.

2. resolved Apr 07, 2025, 07:08 PM UTC

   After investigation, we've determined this was a false alarm triggered by internal monitoring. There is no impact to customer recordings, and all services are functioning as expected. A summary of the incident will be posted within the next three US business days.

3. postmortem Apr 15, 2025, 03:49 AM UTC

   Around 2025-04-07 16:00 UTC, our monitoring systems flagged increased error activity related to Google Meet recordings. Upon investigation, we determined that these were false alerts, triggered by a recent change in Google Meet’s behavior that treated Clari Copilot being denied entry into meetings as failures.The alerts were cleared and the incident was resolved by 19:16 UTC on the same day. All Google Meet calls during this period were recorded as expected, and no user data was at risk.

Read the full incident report →

Started Apr 04, 2025, 11:07 AM UTC· resolved Apr 04, 2025, 12:33 PM UTC

1. investigating Apr 04, 2025, 11:07 AM UTC

   Dialer service is currently unavailable. Our engineering team is actively investigating.

2. identified Apr 04, 2025, 11:42 AM UTC

   Our engineering teams have identified the issue and are implementing a fix.

3. monitoring Apr 04, 2025, 11:59 AM UTC

   Our engineering teams have resolved the issue and we are monitoring the fix.

4. resolved Apr 04, 2025, 12:33 PM UTC

   We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

5. postmortem Apr 09, 2025, 08:25 PM UTC

   On April 4, 2025, at 11:00 UTC, OmniDialer users experienced call failures and received the error message, "We are sorry, an error has occurred." This issue prevented users from successfully initiating calls through the Dialer application. The Clari Engineering team promptly investigated the incident and identified a recent code change as the root cause. This change was rolled back and the issue was resolved at 12:33 UTC on the same day.

Read the full incident report →