Clari Outage History

Started Sep 15, 2026, 08:39 PM UTC· resolved Sep 15, 2026, 10:01 PM UTC

1. investigating Sep 15, 2026, 08:39 PM UTC

   Some customers may be seeing problems with Dashboard, Forecasting and Inspection Our engineering team is actively investigating.

2. monitoring Sep 15, 2026, 09:17 PM UTC

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

3. resolved Sep 15, 2026, 10:01 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.

Read the full incident report →

Started Sep 08, 2026, 07:57 PM UTC· resolved Sep 09, 2026, 12:39 PM UTC

1. monitoring Sep 08, 2026, 07:57 PM UTC

   Our engineering teams are aware of this issue related to a third-party outage and are monitoring the progress of that issue. Smart summaries are not being generated for Copilot calls. Call processing is still working and summaries will be generated once the outage is resolved.

2. resolved Sep 09, 2026, 12:39 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 Sep 11, 2026, 01:13 PM UTC

   On 2026-09-08 from approximately 18:30-20:30 UTC, an outage at a third-party streaming data provider disrupted the pipeline that generates Copilot smart summaries, preventing call summary generation. Call recording and transcription continued to work normally. Once the provider resolved the issue, our systems resumed processing automatically and a backfill job completed on 2026-09-09, generating summaries for all eligible affected calls.

Read the full incident report →

Started Sep 08, 2026, 03:11 PM UTC· resolved Sep 08, 2026, 04:23 PM UTC

1. investigating Sep 08, 2026, 03:11 PM UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

2. monitoring Sep 08, 2026, 04:11 PM UTC

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

3. resolved Sep 08, 2026, 04:23 PM UTC

   The Auto Scaling group failed to launch new instances due to an AMI build configuration issue. Following image remediation, instances are deploying successfully, system latency has normalized, and the Auto Scaling group has returned to a healthy state.

Read the full incident report →

Started Sep 02, 2026, 03:25 PM UTC· resolved Sep 02, 2026, 04:14 PM UTC

1. investigating Sep 02, 2026, 03:25 PM UTC

   We are currently investigating this issue.

2. resolved Sep 02, 2026, 04:14 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 Sep 11, 2026, 03:01 PM UTC

   On 2026-09-02 between approximately 07:57-09:16 UTC, some users were unable to sign in to Clari applications. The incident was triggered by an administrative change that unexpectedly impacted authentication for Clari users. Our teams restored normal authentication service, and all Clari services are currently operating normally.

Read the full incident report →

Started Aug 17, 2026, 05:56 PM UTC· resolved Aug 25, 2026, 09:05 PM UTC

1. investigating Aug 17, 2026, 05:56 PM UTC

   We have received reports from customers that their Salesforce integration user is being disconnected due to token expiration. Our engineering team is actively investigating.

2. investigating Aug 18, 2026, 03:24 PM UTC

   We have received reports from customers that their Salesforce integration user is being disconnected due to token expiration. Our engineering team is actively investigating. If your integration user has been disconnected, you can reconnect to resolve. If you need help, please reach out to Support to get assistance.

3. monitoring Aug 19, 2026, 05:12 PM UTC

   The problem appears to have been a one-time event with Salesforce. We continue to monitor for any recurrence and are actively engaged with Salesforce support to understand what happened and how to avoid further occurrences. We will leave this record in "monitoring" state until we have a satisfactory understanding about the incident but do not expect to make further updates.

4. resolved Aug 25, 2026, 09:05 PM UTC

   We have confirmed from Salesforce what caused the outage for the impacted users. A summary of the incident will be posted within the next three US business days.

5. postmortem Aug 28, 2026, 04:39 PM UTC

   On 2026-08-16, a Salesforce Hyperforce migration caused connection interruptions between Salesforce and Clari across a small group of customer accounts. This issue temporarily paused automated data updates for some organizations and required their users reauthenticate with Salesforce. There is no known way to avoid this situation for future Hyperforce migrations, but we continue to work with Salesforce to explore options.

Read the full incident report →

Started Aug 05, 2026, 10:50 AM UTC· resolved Aug 05, 2026, 01:54 PM UTC

1. identified Aug 05, 2026, 10:50 AM UTC

   *** DO NOT USE AS IS. USE VERBIAGE TO UPDATE EXISTING INCIDENT *** Our engineering teams have identified the issue and are implementing a fix. Some or all the pages are not loading . The next status update will be after the fix has been applied.

2. identified Aug 05, 2026, 12:44 PM UTC

   Our engineering teams have identified the issue and are implementing a fix. Some or all the pages are not loading The next status update will be after the fix has been applied.

3. monitoring Aug 05, 2026, 12:52 PM UTC

   Issue have been fixed , we are monitoring the fix . We observed services is coming back online , no failing cases in last 15 minutes .

4. monitoring Aug 05, 2026, 01:29 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Aug 05, 2026, 01:54 PM UTC

   We have confirmed the issue has been resolved for the impacted users. No new errors have been observed in last 60 minutes of monitoring. All the impacted components are fully operational now. A summary of the incident will be posted within the next three US business days.

6. postmortem Aug 07, 2026, 01:49 PM UTC

   At approximately 2026-08-05 00:02 UTC, a subset of organizations experienced errors when attempting to access the Clari application. Affected users saw the message: "Something went wrong with loading application resources." Our engineering team identified a regression introduced in a recent deployment and issued a hotfix. Systems returned to normal operations at 2026-08-05 13:30 UTC . No customer data was at risk at any point during this incident.

Read the full incident report →

Started Jul 27, 2026, 03:07 PM UTC· resolved Jul 27, 2026, 07:41 PM UTC

1. investigating Jul 27, 2026, 03:07 PM UTC

   We are currently investigating reports of intermittent access issues with the Clari platform. Customers may experience difficulty accessing the application or encounter slow performance. Our engineering team is actively working to resolve this issue. We will provide updates as more information becomes available.

2. monitoring Jul 27, 2026, 03:25 PM UTC

   Our engineering teams have resolved the issue and system performance is returning to normal. We are continuing to monitoring the fix.

3. resolved Jul 27, 2026, 07:41 PM UTC

   After monitoring the issue for 3 hours, we have not seen any reoccurrences and the platform has been stable. A summary of the incident will be posted within the next three US business days.

4. postmortem Jul 29, 2026, 07:05 PM UTC

   At approximately 2026-07-27 13:15 UTC some users experienced long page load times and errors when trying to use the Clari application. The engineering team was able to determine that a problem with scaling some of our cloud-based services was the source of the problem and deployed a fix to restore system performance. Systems returned to normal operations as of 2026-07-27 15:30 UTC and no customer data was at risk during the outage.

Read the full incident report →

Started Jul 13, 2026, 03:18 PM UTC· resolved Jul 15, 2026, 11:08 AM UTC

1. investigating Jul 13, 2026, 03:18 PM UTC

   Some customers may be experiencing issues with Clari Copilot call recordings in Zoom. Our engineering team is actively investigating.

2. investigating Jul 13, 2026, 08:19 PM UTC

   Our engineering team is still actively investigating. The issue is impacting customers relying on web-based recorders for Zoom recordings. We will provide another update as soon as more information is available.

3. investigating Jul 14, 2026, 08:15 AM UTC

   The impacted customers continue to see issues with web-based recorders on Zoom. Our engineering team is actively investigating with Zoom support and reviewing alternative paths for the impacted customers to resume recording functionality. We will provide another update as soon as more information is available.

4. investigating Jul 14, 2026, 05:25 PM UTC

   The issue is still under investigation. Impacted customers continue to experience issues with web-based recorders on Zoom. Our investigation indicates that recent changes in Zoom’s platform behavior are preventing some recorders from joining customer meetings. Our engineering team is actively working with Zoom Support to resolve the issue. We will provide another update as soon as more information becomes available.

5. identified Jul 14, 2026, 06:30 PM UTC

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

6. identified Jul 14, 2026, 10:53 PM UTC

   We have published in-app guidance directing affected customers to reconnect their Zoom integration in Clari Copilot, allowing customers to restore Copilot's ability to record Zoom meetings.

7. monitoring Jul 15, 2026, 07:11 AM UTC

   We have worked with Zoom to resolve the issue affecting web-based recorders. Recordings are now functioning as expected. Our engineering team is monitoring the system, and we will provide another update if anything changes. For impacted customers, including those who previously reconnected their Zoom integration, no further action is needed. If you are still experiencing issues, please contact our support team.

8. resolved Jul 15, 2026, 11:08 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.

9. postmortem Jul 20, 2026, 01:09 PM UTC

   Starting at approximately 06:30 UTC on July 13, 2026, a change in Zoom's platform affected the ability of Clari Copilot's Zoom web recorder to join and record meetings. As a result, some customers were unable to record Zoom meetings in Copilot during the impacted period. This issue impacted only Zoom web-based recording; other recorder platforms were not affected. Meetings scheduled for recording during this period may not have been recorded. Upon identifying the issue, the Clari engineering team worked closely with Zoom to investigate the change, determine its impact, and implement the necessary mitigations. Zoom web recorder joins have returned to normal operation, and we confirmed full recovery by approximately 06:30 UTC on July 15, 2026. We are continuing to work with Zoom to better understand the change and to strengthen our integration so that similar platform changes can be handled more gracefully in the future.

Read the full incident report →

Started Jun 22, 2026, 02:51 PM UTC· resolved Jun 24, 2026, 01:48 AM UTC

1. investigating Jun 22, 2026, 02:51 PM UTC

   Our engineering team is actively investigating.

2. identified Jun 22, 2026, 03:39 PM UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

3. identified Jun 22, 2026, 04:03 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Jun 22, 2026, 05:40 PM UTC

   We identified a few changes from the Copilot Infrastructure maintenance on Saturday June 20th that caused some recorders to fail. We have fixed the issue and are continuing to monitor the system. We will provide another update end of day tomorrow before we resolve this incident.

5. identified Jun 22, 2026, 05:56 PM UTC

   We have identified that we are not showing the consent page during call recordings. We are working on a fix and will provide an update as soon as the issue is resolved.

6. monitoring Jun 22, 2026, 06:40 PM UTC

   We have resolved the issue that was preventing the consent page from displaying during call recordings. We are continuing to monitor the system after the Copilot Infrastructure maintenance on Saturday June 20th and we will provide another update by the end of day tomorrow before we resolve this incident.

7. monitoring Jun 23, 2026, 06:20 PM UTC

   We are continuing to monitor this issue and will leave this incident open until the end of the day. If no further issues are observed by that time, we will resolve the incident. If you are continuing to see any issues with the Copilot platform please reach out to the Clari customer support team.

8. resolved Jun 24, 2026, 01:48 AM UTC

   After monitoring Copilot performance throughout the day and not seeing any reoccurrence of the issues the Clari Engineering team is marking this incident as resolved.

9. postmortem Jun 26, 2026, 03:19 PM UTC

   Beginning around 08:23 UTC on 2026-06-22 some Clari Copilot customers experienced failures across Zoom, Google Meet, and Microsoft Teams that prevented calls from being recorded. The errors were traced back to the Copilot maintenance on 2026-06-20 and configuration changes that were not fully applied. The Clari Engineering team remediated the issue by applying the configuration changes and validating the changes. Call recording functionality was restored at approximately 18:40 UTC 2026-06-22. We continued to monitor the system for the next 24 hours to ensure that there were no further issues before resolving the incident.

Read the full incident report →

Started Jun 22, 2026, 10:39 AM UTC· resolved Jun 22, 2026, 11:48 AM UTC

1. investigating Jun 22, 2026, 10:39 AM UTC

   Our engineering team is actively investigating the root cause across all three platforms. We're monitoring call recording success rates closely and will provide updates as we learn more.

2. resolved Jun 22, 2026, 11:48 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.

3. postmortem Jul 21, 2026, 07:05 PM UTC

   Beginning around 08:23 UTC on 2026-06-22 some Clari Copilot customers experienced failures across Zoom, Google Meet, and Microsoft Teams that prevented calls from being recorded. The errors were traced back to the Copilot maintenance on 2026-06-20 and configuration changes that were not fully applied. The Clari Engineering team remediated the issue by applying the configuration changes and validating the changes. Call recording functionality was restored at approximately 18:40 UTC 2026-06-22. We continued to monitor the system for the next 24 hours to ensure that there were no further issues before resolving the incident.

Read the full incident report →

Started Jun 06, 2026, 12:16 AM UTC· resolved Jun 06, 2026, 04:14 AM UTC

1. investigating Jun 06, 2026, 12:16 AM UTC

   Clari is currently experiencing longer load times and errors than normal. Our engineering team is actively investigating the issue.

2. investigating Jun 06, 2026, 03:15 AM UTC

   The engineering team is continuing to investigate the issue. At this time users may still be experiencing longer page load times or increased errors.

3. resolved Jun 06, 2026, 04:14 AM UTC

   We have identified and fixed a problem that was overloading database queries and resulted in slow performance throughout the application. All systems should be functioning normally again.

4. postmortem Jun 10, 2026, 11:23 PM UTC

   At approximately 23:44 on 2026-06-05 UTC some Clari users experienced long page load times and errors when trying to use the application. The Clari Engineering team was able to determine that a database operation was continually executing and overloading one of the databases. Once the database call was stopped and the stuck connections were cleared, system performance was able to return to normal at around 04:33 on 2026-06-06 UTC.

Read the full incident report →

Started Jun 04, 2026, 03:53 PM UTC· resolved Jun 05, 2026, 09:14 AM UTC

1. investigating Jun 04, 2026, 03:53 PM UTC

   Some customers may be seeing problems with connectivity to Clari Copilot Our engineering team is actively investigating.

2. investigating Jun 04, 2026, 04:21 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 05, 2026, 05:06 AM UTC

   Update: Resolution Requires Customer Action Our engineering teams have resolved the issue and we are monitoring the fix. However, customers who continue to experience an impact must take action to fully restore functionality. Required Action: Salesforce Administrators (Role: Full System Administrator) must: * Navigate to **Workspace Settings > Integrations** in Clari Copilot. * Re-authenticate the Salesforce integration. Resolution Process: After re-authentication - Our systems will automatically re-sync your Salesforce data from the impacted window. - Full functionality will be restored within the following hours. Who Should Take Action: Customers who continue to experience Salesforce CRM connectivity issues after this update. If you encounter any issues or need assistance during the re-authentication process, please reach out to our Support Team.

4. resolved Jun 05, 2026, 09:14 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.

5. postmortem Jun 11, 2026, 06:45 AM UTC

   Starting at approximately 15:25 on 2026-06-04 UTC, a code defect in Clari Copilot's internal integration maintenance process caused Salesforce integrations to become disconnected for a subset of customers. This impacted Salesforce data sync only. All other Copilot functionality continued to operate normally. The Clari engineering team identified the cause and rolled out a fix at 18:29 on 2026-06-04 UTC. Affected customers were provided re-authentication instructions to restore their Salesforce connection, after which full functionality resumed. No customer data was lost during this incident

Read the full incident report →

Started Jun 03, 2026, 10:27 AM UTC· resolved Jun 03, 2026, 12:54 PM UTC

1. investigating Jun 03, 2026, 10:27 AM UTC

   Some customers using Copilot with Google Meet are not seeing their meetings recorded. Our engineering team is actively investigating.

2. identified Jun 03, 2026, 12:07 PM UTC

   Our engineering teams have identified the issue and are implementing a fix. Due to a recent change on Google Meet copilot bots are unable to join some of the Google Meet meetings. Team has found a fix and is working on implementing it. The next status update will be after the fix has been applied.

3. monitoring Jun 03, 2026, 12:47 PM UTC

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

4. resolved Jun 03, 2026, 12:54 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 Jun 06, 2026, 10:43 AM UTC

   Starting at approximately 02:00 on 2026-06-02 UTC Google began rolling out a change that was incompatible with Clari Copilot Google Meet recorder bots. This impacted a subset of customers using Google Meet preventing the bots from joining calls. Clari engineering team identified the change and rolled out a fix at 12:47 2026-06-03 UTC resolving the issue.

Read the full incident report →

Started May 11, 2026, 07:05 PM UTC· resolved May 11, 2026, 08:25 PM UTC

1. investigating May 11, 2026, 07:05 PM UTC

   The Clari Revenue platform is currently seeing an increase in errors in Inspection and Forecasting modules. Our engineering team is actively investigating the issue.

2. monitoring May 11, 2026, 07:36 PM UTC

   Our engineering teams have implemented a fix which has addressed the observed errors. We are monitoring the system to confirm the issue has been resolved. The next status update will be when remediation efforts are complete or the state of this incident otherwise changes.

3. resolved May 11, 2026, 08:25 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 May 14, 2026, 12:15 AM UTC

   On 2026-05-11 at approximately 18:55 UTC, a number of Clari customers encountered errors connecting to the Salesforce integration within the Clari application. Engineers identified a configuration change that enabled a 30-day idle timeout for Salesforce refresh tokens, which caused integration user sessions to be invalidated and disconnected across multiple organizations. The setting was disabled at approximately 19:15 UTC, after which availability began recovering. Full service availability was confirmed for all affected organizations by approximately 20:52 UTC. Other areas of the Clari application were unaffected during this time.

Read the full incident report →

Started May 08, 2026, 04:39 AM UTC· resolved May 08, 2026, 10:50 AM UTC

1. monitoring May 08, 2026, 04:39 AM UTC

   CRM syncing is showing a delay of a a few hours. we expect the delay to be caught up by 8:00 AM UTC

2. monitoring May 08, 2026, 09:32 AM UTC

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

3. resolved May 08, 2026, 10:50 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 14, 2026, 07:04 PM UTC

   On 2025-05-08 at approximately 02:52 UTC, customers experienced delays of several hours with RevDB CRM sync jobs due to an internal service connectivity issue impacting the workflow system responsible for processing syncs. The affected services were restored and the backlog was fully cleared. No data was lost or compromised during the incident. Additional monitoring and recovery safeguards have since been implemented to reduce the risk of recurrence.

Read the full incident report →

Started Apr 15, 2026, 03:48 PM UTC· resolved Apr 15, 2026, 04:29 PM UTC

1. investigating Apr 15, 2026, 03:48 PM UTC

   Groove is currently experiencing intermittent performance issues, and you may notice some slowness. Our engineers are actively investigating and will share updates as soon as possible.

2. monitoring Apr 15, 2026, 04:01 PM UTC

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

3. resolved Apr 15, 2026, 04:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 09, 2026, 03:36 PM UTC· resolved Apr 09, 2026, 06:32 PM UTC

1. investigating Apr 09, 2026, 03:36 PM UTC

   Our engineering team is actively investigating reported issues with the Analytics module.

2. monitoring Apr 09, 2026, 04:21 PM UTC

   We have identified and reverted the related change. Behavior is returning to normal and we will continue to monitor system health.

3. resolved Apr 09, 2026, 06:32 PM UTC

   We have confirmed the issue has been resolved for all impacted users. A summary of the incident will be posted.

4. postmortem Apr 10, 2026, 11:09 PM UTC

   On 2026-04-09 at approximately 14:48 UTC, users were unable to load Analytics modules in the Clari application. Clari engineers quickly identified the cause and took action to restore the affected functionality. During this time, a small number of other areas of the application were also impacted as a result of the same underlying issue. Engineers performed rolling restarts of the affected Analytics services, restoring full Analytics module availability by approximately 16:21 UTC. Isolated issues in a small number of other dependent services were subsequently identified and resolved through additional targeted restarts, with all issues fully cleared by 17:52 UTC.

Read the full incident report →

Started Apr 08, 2026, 07:26 PM UTC· resolved Apr 08, 2026, 11:40 PM UTC

1. investigating Apr 08, 2026, 07:26 PM UTC

   Our engineering team is actively investigating reports of the Forecasting tab not appearing for some customers.

2. identified Apr 08, 2026, 07:54 PM UTC

   We have identified the cause of the missing Forecasting tabs and are working to resolve.

3. monitoring Apr 08, 2026, 08:32 PM UTC

   We have restored the Forecasting tab and are monitoring to confirm that all users have access.

4. resolved Apr 08, 2026, 11:40 PM UTC

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

5. postmortem Apr 09, 2026, 09:08 PM UTC

   On 2026-04-08 at approximately 18:53 UTC, all Clari customers lost access to the Forecast tab in the Clari application. Other areas of the application were unaffected and continued to operate normally. Clari engineers quickly identified the cause as the unintended deletion of configuration data required to display the Forecast tab, and restored the affected data. During the restoration process, there was a brief period of increased latency as service capacity scaled back up to handle returning traffic. Full access to the Forecast tab was confirmed for all affected users by 23:20 UTC.

Read the full incident report →

Started Mar 27, 2026, 07:44 AM UTC· resolved Mar 27, 2026, 03:04 PM UTC

1. investigating Mar 27, 2026, 07:44 AM UTC

   Clari Copilot users are currently not receiving any email notifications. Our engineering team is actively investigating the issue. The issue is only limited to the Clari Copilot product.

2. investigating Mar 27, 2026, 02:26 PM UTC

   We are continuing to investigate the issue. Email notifications remain impacted.

3. resolved Mar 27, 2026, 03:04 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 Mar 30, 2026, 07:18 AM UTC

   At 14:30 UTC on March 25, 2025, Clari Copilot experienced an interruption in email notifications due to an exhausted email delivery quota. As a result, email notifications scheduled during this period were not delivered. Clari was able to increase the delivery limit and service was fully restored as of 14:55 UTC on March 27, 2025. All systems are now performing as expected and emails are being delivered. Please note that missed notifications from the outage window cannot be retroactively delivered. At no time during this incident was user data at risk.

Read the full incident report →

Started Mar 04, 2026, 06:43 PM UTC· resolved Mar 05, 2026, 03:10 PM UTC

1. investigating Mar 04, 2026, 06:43 PM UTC

   We are currently investigating an issue where Clari Copilot is not recording some Zoom calls

2. investigating Mar 04, 2026, 09:07 PM UTC

   Some Clari Copilot calls via Zoom continue to not be recorded. Our engineering team is currently working with Zoom to resolve this issue.

3. investigating Mar 05, 2026, 05:24 AM UTC

   We are continuing to work with the Zoom engineering team to resolve this issue. We will provide additional details about the progress as they become available.

4. monitoring Mar 05, 2026, 11:57 AM UTC

   Our engineering teams have resolved the issue together with the Zoom engineering team and we are monitoring the fix.

5. resolved Mar 05, 2026, 03:10 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 Mar 09, 2026, 11:55 PM UTC

   At approximately 2026-03-04 15:00 UTC, a subset of Clari Copilot customers experienced an issue where the recording bot was unable to join Zoom meetings. This was caused by an account authentication error within the Zoom platform that prevented the bot from successfully joining calls. This was a reoccurrence of the issue that prevented Copilot from joining Zoom calls on 2026-02-11 and was caused by Zoom not fully updating the Copilot authentication across their entire platform. The Clari engineering team worked with Zoom’s Support and Development team to correctly update the authentication process platform wide and resolve the issue. An RCA from Zoom on this issue is pending. Recording functionality was fully restored and confirmed operational at 2026-03-05 11:28 UTC.

Read the full incident report →

Started Feb 11, 2026, 12:29 AM UTC· resolved Feb 11, 2026, 02:53 PM UTC

1. monitoring Feb 11, 2026, 12:29 AM UTC

   We’re aware of an issue affecting links in some email content, and our engineering teams are actively working to resolve it as quickly as possible.

2. monitoring Feb 11, 2026, 02:19 AM UTC

   We've spotted that something has gone wrong. We're currently working our partners to remediate the issue, and will provide an update soon.

3. monitoring Feb 11, 2026, 02:38 PM UTC

   We’re aware of an issue affecting links in some email content,. We're actively working with our partners to remediate the issue, and will provide an update soon.

4. resolved Feb 11, 2026, 02:53 PM UTC

   The issue affecting links in some email content, has been resolved. Thank you for your patience and understanding.

5. postmortem Feb 13, 2026, 09:50 PM UTC

   Around 2026-02-11 09:51 UTC an issue affecting links in some email content resulted in bounced or spam-foldered emails by a third party vendor \(Google\). The team has worked closely with the vendor \(Google\) and successfully remediated the situation by 2026-02-12 06:00 UTC.

Read the full incident report →

Started Feb 04, 2026, 09:14 PM UTC· resolved Feb 09, 2026, 01:30 PM UTC

1. investigating Feb 04, 2026, 09:14 PM UTC

   We are investigating an issue where Clari Copilot is not recording calls made via Zoom for some customers.

2. monitoring Feb 04, 2026, 11:11 PM UTC

   Our engineering team has put in place a temporary workaround and are working with the external vendor for a long term solution.

3. monitoring Feb 05, 2026, 02:14 PM UTC

   The issue continues to impact a subset of our customers despite the workaround. Some users will see a consent prompt before recording begins, which is expected. We are investigating the recent failures and will provide updates as they become available.

4. monitoring Feb 06, 2026, 06:36 PM UTC

   The investigation continues and updates will be provided as new information becomes available.

5. resolved Feb 09, 2026, 01:30 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 Feb 12, 2026, 05:44 AM UTC

   At 11:11 UTC on February 4, 2026, a subset of Clari Copilot customers experienced an issue where the recording bot was unable to join Zoom meetings. This was caused by an account authentication error with the Zoom platform that prevented the bot from successfully joining calls.The Clari engineering team worked with Zoom’s development team to update the authentication process and resolve the issue. Recording functionality was fully restored and confirmed operational at 12:05 UTC on February 9, 2026. We regret that scheduled calls for impacted customers during this window were not recorded.

Read the full incident report →

Started Jan 14, 2026, 01:42 PM UTC· resolved Jan 14, 2026, 03:56 PM UTC

1. investigating Jan 14, 2026, 01:42 PM UTC

   A recent update to eliminate duplicate columns in the opportunity grid has caused the grid columns to become re-ordered for some customers. Our engineering team is actively investigating.

2. identified Jan 14, 2026, 02:06 PM UTC

   Our engineering teams have identified the issue and are implementing a fix. The change to eliminate duplicate columns had the undesired side-effect of changing the ordering of the remaining columns. The team is working to roll back the change. The next status update will be after the fix has been applied.

3. resolved Jan 14, 2026, 03:56 PM UTC

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

4. postmortem Jan 16, 2026, 05:01 AM UTC

   On 2026-01-14 at approximately 08:00 UTC, Clari made a system update that caused the user-defined column order in Opportunity Grid saved views to be re-ordered or reverted to the default column ordering. The issue caused workflow disruption and inconvenience for users but did not block core business operations or impact data integrity. At 2026-01-14 15:52 UTC the Clari Engineering team successfully reverted the change and all user-defined saved views were restored.

Read the full incident report →

Started Jan 12, 2026, 05:08 PM UTC· resolved Jan 12, 2026, 06:19 PM UTC

1. investigating Jan 12, 2026, 05:08 PM UTC

   Some customers may be seeing errors in Opportunity and Analytics modules and/or Forecasting data will be zero'd out. Our engineering team is actively investigating

2. resolved Jan 12, 2026, 06:19 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 Jan 14, 2026, 02:43 AM UTC

   Starting around 2026-01-11 at 02:45 UTC, a few Clari customers may have seen page load errors when attempting to access areas of the app including Forecasting and Analytics. This was caused by an error introduced while preparing these customers for migration to RevDB. Clari Engineering corrected the database entries and the impacted customers were fully restored by 2026-01-12 18:15 UTC. No customer data was impacted and there is no impact to any RevDB migrations.

Read the full incident report →

Started Jan 05, 2026, 04:32 PM UTC· resolved Jan 05, 2026, 10:15 PM UTC

1. investigating Jan 05, 2026, 04:32 PM UTC

   We are investigating delays in loading CRM and Activity data for modules that leverage RevDB.

2. investigating Jan 05, 2026, 05:31 PM UTC

   The investigation into RevDB loading delays is ongoing. Customers may see delays loading new CRM and Activity data.

3. investigating Jan 05, 2026, 06:22 PM UTC

   Investigation and mitigation continues. Customers may still see delays loading new CRM and Activity data.

4. monitoring Jan 05, 2026, 08:05 PM UTC

   The root cause of the loading delays has been identified and fixed. Data loading for customers is catching back up and we continue to monitor the system.

5. resolved Jan 05, 2026, 10:15 PM UTC

   Data loading delays have been resolved.

6. postmortem Jan 07, 2026, 10:08 PM UTC

   On 2026-01-05 at approximately 13:50 UTC, Clari experienced an interruption in the processing of CRM and Activity data into RevDB. Due to database locking issues across multiple clusters, live CRM and Activity updates stalled for some customers, resulting in data freshness delays of roughly 2 to 5 hours. The impact was limited to delayed data updates; the application experience was unaffected, and no customer data was lost. Clari engineers identified a buildup of long-running, idle-in-transaction database sessions that were causing lock contention. The problematic sessions were terminated, unblocking the affected clusters and allowing CRM and Activity ingestion to resume. To reduce the likelihood of this issue recurring, Clari has implemented changes to prevent idle sessions from accumulating, and we are strengthening monitoring and alerting for database lock behavior to detect and quickly mitigate similar conditions.

Read the full incident report →