MyCase had 10 outages in the last 2 years totaling 46h 43m of downtime — averaging 0.4 incidents per month.
There were 10 MyCase outages since June 10, 2025 totaling 46h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We’re continuing to work on bringing our systems fully back on track following a major outage at our cloud provider, who are still experiencing a partial service disruption. While recovery progresses, customers may continue to experience slowness or degraded performance across parts of the system. We’ll post more updates as they become available.
We are aware of customers seeing slow response times within the MyCase app and/or increased timeouts. This is the result of an ongoing incident with our cloud provider, AWS, and we are closely monitoring the situation to restore operations to normal as quickly as we can. We appreciate your continued patience in this matter.
We are continuing to monitor this incident with our cloud provider, AWS.
We are continuing to monitor this incident with our cloud provider, AWS.
We are continuing to monitor this incident with our cloud provider, AWS. The incident persists, but gradual improvement is noted with login attempts and application navigation.
This incident has been resolved.
MyCase is currently experiencing degraded performance of the Search feature for some users. Our Development Team is aware of this issue and working as quickly as possible to resolve it. Please check back on this page, and we will provide an update shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.