Caseware Cloud incident
Caseware Cloud-based Engagement Solutions Firm Authoring (including Enterprise) is experiencing Degraded Performance for United States.
Caseware Cloud experienced a major incident on October 20, 2025 affecting Cloud-based Engagement Solutions, lasting 1d 4h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 08:05 PM UTC
Our teams are working to identify the root cause and determine the necessary corrective actions. We continue to experience unavailability of our firm Authoring (including Enterprise) at this time. An update will be provided within the hour.
- investigating Oct 20, 2025, 09:16 PM UTC
Our teams are working to identify the root cause and determine the necessary corrective actions. We continue to experience unavailability of our firm Authoring (including Enterprise) at this time. An update will be provided within the hour.
- investigating Oct 20, 2025, 09:17 PM UTC
Our teams are working to identify the root cause and determine the necessary corrective actions. We continue to experience unavailability of our firm Authoring (including Enterprise) at this time. An update will be provided within the hour.
- monitoring Oct 20, 2025, 09:46 PM UTC
Cloud-based Engagement Solutions in the United States region 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 Oct 20, 2025, 09:48 PM UTC
Cloud-based Engagement Solutions in the United States region 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 Oct 20, 2025, 10:45 PM UTC
Cloud-based Engagement Solutions in the United States region has resumed normal activity. We are continuing to monitor our systems to ensure that there are no residual issues. We will continue to provide updates as necessary.
- resolved Oct 21, 2025, 01:10 AM UTC
This incident has been resolved.