Aderant experienced a critical incident on September 2, 2025 affecting iTimekeep US and Onyx US, lasting 10h 21m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 02, 2025, 01:49 PM UTC
We are currently investigating an issue that is affecting logins to the iTimekeep application in the US region.
- investigating Sep 02, 2025, 01:59 PM UTC
We are continuing to investigate this issue.
- monitoring Sep 02, 2025, 02:12 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Sep 02, 2025, 02:29 PM UTC
We continue to monitor and actively address issues as they arise.
- monitoring Sep 02, 2025, 03:13 PM UTC
We are actively resolving an issue affecting logins to the iTimekeep application in the US region.
- monitoring Sep 02, 2025, 03:51 PM UTC
We have identified the likely cause of the degraded performance in iTimekeep. Our investigation indicates that the issue is related to cache population. Our CloudOps team is actively implementing a solution. Once this solution is in place, we will provide a further update on progress and resolution. Thank you for your patience as we work to restore full performance as quickly as possible.
- monitoring Sep 02, 2025, 04:50 PM UTC
Our team continues to work on addressing the cache population. Efforts remain ongoing, and we will provide the next update once progress milestones are reached.
- monitoring Sep 02, 2025, 06:22 PM UTC
The fix is being verified to ensure stability and effectiveness before we apply it to the production environment. We will provide a further update once the rollout begins.
- monitoring Sep 02, 2025, 07:13 PM UTC
The fix has been successfully verified and is now being applied to the production environment. We are monitoring the results. There will be no downtime as part of applying the fix to the production environment.
- monitoring Sep 02, 2025, 08:16 PM UTC
We are in the process of applying the fix to production. We continue to actively monitor the changes to confirm effectiveness and determine if any further efforts are required.
- monitoring Sep 02, 2025, 11:06 PM UTC
We continue to monitor changes made to confirm effectiveness and determine if any further efforts are required.
- resolved Sep 03, 2025, 12:10 AM UTC
The fix mentioned previously has been implemented in Production. Indications are that the incident has been resolved and iTimekeep performance has been restored. If you are still experiencing any degraded performance, please restart iTimekeep Connect. Should issues persist after a restart, contact Aderant Support for further assistance.