Caseware Cloud incident
Caseware Cloud Service - Partial Outage - Sherlock
Caseware Cloud experienced a major incident on January 28, 2026 affecting Sherlock and Sherlock and 1 more component, lasting 1d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jan 28, 2026, 05:12 PM UTC
We are currently experiencing a temporary outage impacting the Issuev2 Sherlock API and the Issuev2 dataset in the Sherlock Reader/Builder. Our engineering team is actively investigating and working on a fix. We will provide updates as progress is made. Thank you for your patience.
- identified Jan 28, 2026, 06:00 PM UTC
We are continuing to work on a fix for this issue.
- identified Jan 28, 2026, 07:24 PM UTC
Our engineering teams remain actively engaged and are making progress toward a fix. We will provide further updates once the fix is deployed tomorrow.
- monitoring Jan 29, 2026, 01:56 PM UTC
The Issuev2 Sherlock API and the Issuev2 dataset in the Sherlock Reader/Builder has resumed normal activity. We are actively monitoring our systems to ensure that there are no residual issues. We will continue to provide updates as necessary.
- monitoring Jan 29, 2026, 05:42 PM UTC
The Issuev2 Sherlock API and the Issuev2 dataset in the Sherlock Reader/Builder has resumed normal activity. We are actively monitoring our systems to ensure that there are no residual issues. We will continue to provide updates as necessary.
- resolved Jan 29, 2026, 06:46 PM UTC
The Issuev2 Sherlock API and the Issuev2 dataset within the Sherlock Reader/Builder are operating normally. Post-resolution monitoring has completed successfully. At this time, the incident is considered fully resolved. We apologize for any inconvenience.