Clari Outage History

The Clari Revenue Platform experienced increased errors in its Inspection and Forecasting modules, affecting the Forecast, Opportunities, and Inspect components for 1.4 hours. The engineering team implemented a fix that resolved the errors for impacted users. The incident was fully resolved after a monitoring period to confirm system stability.

Clari experienced a major incident where CRM syncing was delayed by several hours, affecting data synchronization for users. The engineering team resolved the underlying issue and confirmed that the syncing delays were caught up. The incident lasted 6.3 hours and was fully resolved with continued monitoring to ensure stability.

Groove experienced intermittent performance issues causing slowness for users, affecting the Clari Revenue Database (RevDB) and Clari Revenue Platform. The engineering team investigated and resolved the issue after 41 minutes of monitoring the fix.

Clari's Analytics module experienced functionality issues that affected the Analyze component for 3 hours. The engineering team identified and reverted a problematic change that was causing the issues. System behavior returned to normal with continued monitoring of system health.

The Clari Forecasting tab disappeared for some users, preventing access to forecast functionality. The engineering team identified and resolved the underlying cause, restoring the tab for all affected users. The incident lasted 4.3 hours from initial reports to full resolution.

Clari Copilot users experienced a complete outage of email notifications for 7.4 hours. The issue was isolated to the Clari Copilot product and did not affect other Clari services. The engineering team investigated and resolved the problem, restoring email notification delivery to all impacted users.

Clari Copilot experienced an issue where some Zoom calls were not being recorded properly, affecting the Copilot service for impacted users. The engineering teams from both Clari and Zoom collaborated to identify and resolve the underlying integration problem. After 20.5 hours, the issue was fixed and confirmed resolved for all affected users.